Difference between revisions of "Category talk:OWASP CSRFGuard Project"

From OWASP
Jump to: navigation, search
(How are standard browser navigation functions affected?)
 
(BIRT viewer support ?: new section)
Line 2: Line 2:
  
 
Also, I would assume that re-authentication would be necessary for bookmarked pages. Does it handle these well, or does it choke on an invalid (not blank) request token?
 
Also, I would assume that re-authentication would be necessary for bookmarked pages. Does it handle these well, or does it choke on an invalid (not blank) request token?
 +
 +
== BIRT viewer support ? ==
 +
 +
Does this support BIRT viewer?
 +
 +
Is it able to modify request and response from page generated with <birt:viewer> tag?

Revision as of 13:20, 10 March 2009

How does this affect certain standard browser navigation features? Specifically, does this break the "Back," "Forward," and "Reload/Refresh" buttons?

Also, I would assume that re-authentication would be necessary for bookmarked pages. Does it handle these well, or does it choke on an invalid (not blank) request token?

BIRT viewer support ?

Does this support BIRT viewer?

Is it able to modify request and response from page generated with <birt:viewer> tag?