[ 
https://issues.apache.org/jira/browse/QPID-7729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15949091#comment-15949091
 ] 

ASF GitHub Bot commented on QPID-7729:
--------------------------------------

Github user alex-rufous commented on the issue:

    https://github.com/apache/qpid-java/pull/3
  
    Hi Jin,
    Thanks a lot for reporting the issue and suggesting a fix.
    I committed the changes for Web Management Console into trunk as part of 
https://issues.apache.org/jira/browse/QPID-7729 . The issue with evaluation of 
context path in WMC should be fixed. However, if you are running http 
management in context path other than '/', the more changes in java code of 
http management would be required to fully respect the context path in redirect 
URLs within LogoutHandlers and AuthenticationHandlers. Do you require those 
changes? Could you please share some details how you run the http management in 
your instances of the Qpid Broker? Do you need merging of the changes into 6.0 
or/and 6.1 branches?
    
    Kind Regards,
    Alex



> [Java Broker, WMC] Fix evaluation of context path in the Web Management 
> Console
> -------------------------------------------------------------------------------
>
>                 Key: QPID-7729
>                 URL: https://issues.apache.org/jira/browse/QPID-7729
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Broker
>    Affects Versions: qpid-java-6.0, qpid-java-6.0.1, qpid-java-6.0.2, 
> qpid-java-6.0.3, qpid-java-6.0.4, qpid-java-6.0.5, qpid-java-6.0.6, 
> qpid-java-6.1, qpid-java-6.1.1, qpid-java-6.1.2
>            Reporter: Alex Rudyy
>            Assignee: Alex Rudyy
>             Fix For: qpid-java-broker-7.0.0
>
>
> The ending slash is missed in the context path evaluated in WMC, when broker 
> context path is not '/'. As result, WMC fails to load.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to