tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 42996] New: - Redirect-to-buffer strategy with nio connector results in blank page
Date Mon, 30 Jul 2007 06:00:41 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=42996>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=42996

           Summary: Redirect-to-buffer strategy with nio connector results
                    in blank page
           Product: Tomcat 6
           Version: unspecified
          Platform: Other
        OS/Version: FreeBSD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Catalina
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: apache@spatula.net


When using Wicket 1.2.6 to post a form, Tomcat 6 appears to prematurely close
the HTTP connection when using the nio connector.  This manifests itself as a
blank page being delivered to the end user.  Viewing the TCP dump, it looks like
after the POST data is delivered, Tomcat just closes the connection.

On other dynamic and static pages, Tomcat behaves as-expected.  This only seems
to be a problem when delivering a page using the redirect-to-buffer form
processing pattern.

Wicket's default form processing strategy is to render the output to a buffer,
issue a redirect to the user, and then display the content of the buffer.  (See
http://cwiki.apache.org/WICKET/render-strategies.html and a long discussion of
the redirect-after-post strategy here:
http://www.theserverside.com/tt/articles/article.tss?l=RedirectAfterPost )

This works as-expected every time with the standard HTTP/1.1 connector.  With
the nio connector it fails about 9 times out of 10.

The workaround is to use only the HTTP/1.1 connector.

I'm not 100% certain that this is a Tomcat bug and not a Wicket bug, but it does
seem to be a consequence of the interaction between the two.  Fortunately,
Wicket is an Apache project now too :-)

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

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


Mime
View raw message