[ https://issues.jboss.org/browse/AS7-1856?page=com.atlassian.jira.plugin.s... ] Heiko Braun commented on AS7-1856: ---------------------------------- I would assume it's a bug. But let's see what Darran thinks about it. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-1856?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse commented on AS7-1856: --------------------------------------- Testing I am unable to create a failure by using a proxy as described in AS7-1504. I have identified a slightly different issue in that when a proxy is used the proxy should not use keep alive connections between the proxy and the AS server which will be addressed under AS7-1861 but no 502 response code. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-1856?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated AS7-1856: ---------------------------------- Fix Version/s: (was: 7.1.0.Alpha1) Forum Reference: http://community.jboss.org/message/618435#618435 (was: http://community.jboss.org/message/618435#618435) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-1856?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse commented on AS7-1856: --------------------------------------- After resolving the one other issue identified I am unable to reproduce - please feel free to ask for this to be re-opened if logging / additional information is available. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-1856?page=com.atlassian.jira.plugin.s... ] u j commented on AS7-1856: -------------------------- The Apache error log shows: [Sun Oct 02 11:18:44 2011] [error] [client xxx] (20014)Internal error: proxy: error reading status line from remote server 127.0.0.1, referer: http://[server_ip]:82/console/App.html [Sun Oct 02 11:18:44 2011] [error] [client xxx] proxy: Error reading from remote server returned by /management, referer: http://[server_ip]:82/console/App.html -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-1856?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated AS7-1856: ---------------------------------- Fix Version/s: 7.1.0.Beta1 Forum Reference: http://community.jboss.org/message/618435#618435 (was: http://community.jboss.org/message/618435#618435) -- 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-1856?page=com.atlassian.jira.plugin.s... ] Jason Greene updated AS7-1856: ------------------------------ Moving all non-critical issues to the CR. If you finish it before we release beta please correct the fix-for version. Thanks -- 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-1856?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse resolved AS7-1856. ----------------------------------- Resolution: Rejected I am marking this issue as Rejected as it is fundamentally an issue of having two different authentication mechanisms on a single content (The /management context). The authentication as configured by Apache is happening first which is causing a response for HTTP BASIC authentication. This request then reaches the application server which sees the Basic header which is not supported so the request is rejected. Testing making a change to the AS to 'ignore' the Basic header and prompt for Digest authentication also fails, the Apache server and browser continue trying to send the Basic authentication header. If the '/management' context is going to be proxied through Apache then Apache should not secure this context at the same time as this same context is secured within AS itself. If the security is disabled on AS7 for the HTTP interface then a secured Apache instance can proxy the requests but in the future this would cause a loss of the ACL / authorization support being added shortly. -- 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