[jboss-jira] [JBoss JIRA] (WFLY-2498) Logout of secured (ssl) admin console setup redirects to http address

[Chris Dolphy (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-2498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris Dolphy updated WFLY-2498:
-------------------------------

           Description: 
Description of problem:
Logging out of an admin console secured with SSL (on port 9443) redirects to http address (e.g. http://localhost:9443/logout?logout) which leads to a Page Not Found error.


  was:
Description of problem:
Logging out of an admin console secured with SSL (on port 9443) redirects to http address (e.g. http://localhost:9443/logout?logout) which leads to a Page Not Found error.

Steps to Reproduce:
1. Setup HTTPS for admin console (I uesd the standalone instructions at  https://access.redhat.com/site/solutions/229963) 
2. Login to admin console (e.g. https://localhost:9443/console)
3. Click logout button and see address bar go to http address.


    Steps to Reproduce: 

Steps to Reproduce:
1. Setup HTTPS for admin console (I uesd the standalone instructions at  https://access.redhat.com/site/solutions/229963) 
2. Login to admin console (e.g. https://localhost:9443/console)
3. Click logout button and see address bar go to http address.

    
>  Logout of secured (ssl) admin console setup redirects to http address
> ----------------------------------------------------------------------
>
>                 Key: WFLY-2498
>                 URL: https://issues.jboss.org/browse/WFLY-2498
>             Project: WildFly
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Web Console
>            Reporter: Chris Dolphy
>            Assignee: Heiko Braun
>
> Description of problem:
> Logging out of an admin console secured with SSL (on port 9443) redirects to http address (e.g. http://localhost:9443/logout?logout) which leads to a Page Not Found error.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira