[ https://issues.jboss.org/browse/AS7-4648?page=com.atlassian.jira.plugin.s... ] Jason Greene commented on AS7-4648: ----------------------------------- Reverse proxying works as expected if ProxyPreserveHost is set -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-4648?page=com.atlassian.jira.plugin.s... ] Jess Sightler commented on AS7-4648: ------------------------------------ In my scenario, the frontent proxy (apache httpd) is exposing the endpoint as SSL. I am also currently testing EAP6B1, though I can try a more recent one to recreate the issue if needed. My rule is rewriting the Location redirect to workaround the earlier issue. apache configurations for this are attached. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-4648?page=com.atlassian.jira.plugin.s... ] Jess Sightler edited comment on AS7-4648 at 4/26/12 4:17 PM: ------------------------------------------------------------- In my scenario, the frontend proxy (apache httpd, reverse proxy mode) is exposing the endpoint as SSL. The JBoss management interface itself is listening on HTTP. I am also currently testing EAP6B1, though I can try a more recent one to recreate the issue if needed. My rule is rewriting the Location redirect to workaround the earlier issue. apache configurations for this are attached. was (Author: jsightler): In my scenario, the frontent proxy (apache httpd) is exposing the endpoint as SSL. I am also currently testing EAP6B1, though I can try a more recent one to recreate the issue if needed. My rule is rewriting the Location redirect to workaround the earlier issue. apache configurations for this are attached. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-4648?page=com.atlassian.jira.plugin.s... ] Jess Sightler commented on AS7-4648: ------------------------------------ I have also attached a screenshot of the requests and headers involved in a problematic scenario. If I hit cancel on the dialog that pops up. The Location header of the first response appears to set the Location header correctly, but the second request (from the redirect) still keeps the first credentials. If I hit cancel, it loads an HTML page that appears to be attempting to do a Javascript redirect back to http://192.168.56.33/. This content-type (as seen in the screenshot) is text/plain, though, so I just see the code on the screen. This is all with Firefox 10.0.4 under RHEL 6.2. I'd be happy to test any scenarios or builds that you think would work better. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-4648?page=com.atlassian.jira.plugin.s... ] Jess Sightler commented on AS7-4648: ------------------------------------ At the moment, everything breaks if I remove those due to other issues with EAPB1. Do you have a build of AS7.x that you can recommend for me to try? I tried this build: https://ci.jboss.org/hudson/job/JBoss-AS-7.x-latest/899/ It failed through the proxy as it tried to load some resource from /management on port 80, though. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-4648?page=com.atlassian.jira.plugin.s... ] Jason Greene commented on AS7-4648: ----------------------------------- I think this might be a console issue with URL generation. Deferring to 7.2 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira