You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2016/09/13 11:05:19 UTC

[Bug 60100] Garbage appended at end of request URL

https://bz.apache.org/bugzilla/show_bug.cgi?id=60100

Mark Thomas <ma...@apache.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |NEEDINFO

--- Comment #1 from Mark Thomas <ma...@apache.org> ---
That is most strange. The sequence:

%20HTTP/1.1%22%20200%20111

decodes to

 HTTP/1.1" 200 111

Which is the string from the end of the access log. I don't see how that ended
up in the request line.

The only place those values are available in that format (the decoded form) is
the access log. But I cannot see how they could end up in the request line. Or
even how the AccessLogValve could corrupt the value of the request line -
especially with the encoding since the AccessLogValve doesn't encode anything.

We are going to need more information to progress this.

When the problem occurred, did all requests fail or just some. Was the a
pattern?

How repeatable is this? I'd like to see a tcpdump of a faulty request to
confirm a=exactly what is on the wire.

What is the architecture of the system. Is it multiple clients connecting
directly to a single Tomcat instance or are the reverse proxies /
load-balancers involved?

-- 
You are receiving this mail because:
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org