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 45812] New: No EOS bucket when using mod_jk with 401 response
Date Mon, 15 Sep 2008 18:25:11 GMT
https://issues.apache.org/bugzilla/show_bug.cgi?id=45812

           Summary: No EOS bucket when using mod_jk with 401 response
           Product: Tomcat 5
           Version: Unknown
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Native:JK
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: Brian.Rectanus@breach.com


I send this to dev list, but received no response:

http://mail-archives.apache.org/mod_mbox/tomcat-dev/200809.mbox/<b61a4e530809081550u242eacaapd5fa7e37c9c3d222@mail.gmail.com>

When mod_jk sends a 401, it is not sending an EOS (sends a FLUSH).  This causes
a module that buffers the response (for example, the mod_security2 module which
I maintain) to not realize the full page has been sent.  This causes httpd to
issue the default 401 response, which does not include the WWW-Authenticate
header and thus no prompt for credentials.

I am able to work around this, but I am confused as to why mod_jk does not send
an EOS.  Is it a bug?  If not, then why and how can a module know mod_jk is
done sending data (other than looking at C-L header)?

Some more info can be found in the ModSecurity issue tracker:

https://www.modsecurity.org/tracker/browse/MODSEC-16

-B


-- 
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: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org


Mime
View raw message