https://issues.apache.org/bugzilla/show_bug.cgi?id=53062
--- Comment #10 from Mark Thomas ---
7.0.30 will be released when it is ready. As a volunteer organization, the ASF
does not commit to release schedules.
What I can say is that I try to do a Tomcat 7 release every month. The first
task is
https://issues.apache.org/bugzilla/show_bug.cgi?id=53062
--- Comment #9 from wansho...@hotmail.com ---
(In reply to comment #8)
> Fixed in trunk and 7.0.x and will be included in 7.0.30 onwards.
>
> I think I have covered all the edge cases but if you spot an edge case you
> think still isn't cor
https://issues.apache.org/bugzilla/show_bug.cgi?id=53062
--- Comment #8 from Mark Thomas ---
Fixed in trunk and 7.0.x and will be included in 7.0.30 onwards.
I think I have covered all the edge cases but if you spot an edge case you
think still isn't correct, it should be easy to extend the unit
https://issues.apache.org/bugzilla/show_bug.cgi?id=53062
--- Comment #7 from Mark Thomas ---
Looking at the code, that certainly looks as if it is the case. The query
string (if any) should be excluded from the normalization process. I'll add
some more unit tests to confirm this is happening and
https://issues.apache.org/bugzilla/show_bug.cgi?id=53062
--- Comment #6 from Konstantin Preißer ---
Hi,
it seems that the URL normalization which has been added to Tomcat 7.0.28
includes the querystring part of the URL in the normalization process.
I'm not 100% sure if the character '/' is allo
https://issues.apache.org/bugzilla/show_bug.cgi?id=53062
Mark Thomas changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://issues.apache.org/bugzilla/show_bug.cgi?id=53062
--- Comment #4 from mgrigorov ---
I have noticed that WebLogic (not sure which version though) also produce such
absolute urls.
If you ask me IE users should suffer just for the reason they use this browser,
but except IE+Tomcat_virtual_hos
https://issues.apache.org/bugzilla/show_bug.cgi?id=53062
--- Comment #3 from Mark Thomas ---
Hmm. Interesting. RFC2396 says /./ and /../ are only special in relative URLs.
It implies (but does not make explicitly clear) that /./ and /../ are to be
treated literally in absolute URLs. That certainl
https://issues.apache.org/bugzilla/show_bug.cgi?id=53062
--- Comment #2 from Mark Thomas ---
The specification says relative URLs must be translated to "fully qualified
URL". My understanding of that is that it means an absolute URL. The
specification says nothing about normalizing or not normali
https://issues.apache.org/bugzilla/show_bug.cgi?id=53062
mgrigorov changed:
What|Removed |Added
CC||mgrigo...@apache.org
--
Configure bug
https://issues.apache.org/bugzilla/show_bug.cgi?id=53062
--- Comment #1 from mgrigorov 2012-04-11 12:44:53 UTC ---
The demo application provides a workaround by using a custom
HttpServletResponseWrapper that solves the problem but I believe this should be
handled by Tomcat itself.
It uses the sam
11 matches
Mail list logo