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 33970] New: - scheme directive borked?
Date Fri, 11 Mar 2005 21:22:16 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=33970>.
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=33970

           Summary: scheme directive borked?
           Product: Tomcat 4
           Version: 4.1.9
          Platform: Sun
        OS/Version: Solaris
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Connector:Coyote HTTP/1.1
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: jbaden@usc.edu


The scheme directive appears to be acting up on the coyote connector in tomcat
4.1.x (tried multiple 4.x flavors).

We have an app that does a fair share of:
   response.sendRedirect(request.getContextPath() +
"/render.userLayoutRootNode.uP");
so we've set
   scheme="https"
in the connector configs.

This 'works' rather sporadically... sometimes we'll get the redirect and
sometimes not, but no pattern is visible, or even reproducible.  Without
explicitly setting the scheme to "https," the redirects are consistently done
via http.

For the record, our setup is such that the https redirect would hit a load
balancer which SSL offloads and transmits to port 80 on apache, which then hands
off to mod_jk/tomcat.

The inconsistency of this whole issue suggests it may be a misconfigured load
balancer, or that the configs across the servers aren't identical, but those
elements have been double and triple checked.

Going through the amount of notes, there appears to be a known issue with
scheme, but nothing conclusive.  If anyone has any suggestions, feedback, or
tips, please drop me a line.  In the meantime, I'll try to reproduce (or more
accurately, hopefully not reproduce) the same issue with 5.x

Thx.

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


Mime
View raw message