https://issues.apache.org/bugzilla/show_bug.cgi?id=35217
Co-Advisor <[EMAIL PROTECTED]> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|INVALID |
--- Comment #6 from Co-Advisor <[EMAIL PROTECTED]> 2008-08-26 09:46:53 PST ---
Comment #5 says:
> Note that (") is defined as a separator.
I do not know whether the problem has been fixed since our original report, but
please note that the request in Comment #4 does not have quotes. The quotes you
see will be eaten by the shell. To Apache, the request looks more like this:
GET http://webproxy.india.sun.com:8000/tst.txt HTTP/1.0\r\n
Cache-Control: max-age=0 =new\r\n
\r\n
which contains a valid max-age directive followed by garbage.
The original test cases (see attachments) do not have this problem.
> So by definition a value such as
> "xxxxx" will be interpreted by stripping away the separators. Thus the value "
> max-age=0 "=blah is interpreted as [max-age=0] [=blah] where the second entry
> is invalid while the first entry is valid cache control directive.
Whether quoted strings are not token-like opaque blobs but regular input (that
apparently should be re-parsed and interpreted!) preceded and followed by a
separator is highly debatable.
IMO, the second original test case leaves little doubt that there was a bug
here because it uses a quoted string in the value of the extension directive.
That usage is a 100% valid extension, right? Again, I do not know whether this
has been fixed since.
HTH.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
