https://issues.apache.org/bugzilla/show_bug.cgi?id=55695
--- Comment #2 from Eugene <johnny...@mail.ru> --- Do you really think that it could be a bug in application? I don't think so. We are using Spring framework, but the bug appears in spring controllers and in tipycal servlets.. Correct me pls, if I'm not right, but, for example, when the client send GET-request to the server, the application receives the HttpServletRequest, parsed first of all by tomcat engine (i don't really know how it's doing it), and then only, in case of spring controller there could be later changes in HttpServletRequest. I suppose that spring can do nothing that is able to clear some parameters that are present in request object. The most strange fact about that story is that after refreshing the page (read - sending the request again) nothing bad happens. The request proceeds correctly. There is no any logic in application connected with filling ServletRequest object's parameters by parsing the request. Also, we didn't define any special settings for tomcat, which can influence on how it processes the request. It's a pity, if it's really the bug in application, cause we don't have any idea about where it could come from and when :( -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
