>From the history of AXIS2-5608 you can see what happened: the "fix"
went into a release and it was later discovered that it caused a
regression elsewhere. Since the change was submitted without a test,
the only sensible option was to roll it back.
Andreas
On Tue, Nov 13, 2018 at 11:47 AM R. Laps
On Tue, Nov 13, 2018 at 4:47 AM R. Lapsien wrote:
> Secure Cookie not returned to WebServer
>
>
> I'm accessing a WebService on an BEA Server from a Java client using AXIS2
> 1.7.8
>
> As can be seen in the SSL trace AXIS2 is not returning the secure cookie
> (named '_WL_AUTHCOOKIE_JSESSIONID') t
[
https://issues.apache.org/jira/browse/AXIS2-5939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Siyana Slavova updated AXIS2-5939:
--
Priority: Critical (was: Major)
> Axis2 not parsing correctly query parameters after upgrading
[
https://issues.apache.org/jira/browse/AXIS2-5939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Siyana Slavova updated AXIS2-5939:
--
Affects Version/s: 1.7.8
> Axis2 not parsing correctly query parameters after upgrading xml sch
[
https://issues.apache.org/jira/browse/AXIS2-5939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Siyana Slavova updated AXIS2-5939:
--
Attachment: Echo.aar
> Axis2 not parsing correctly query parameters after upgrading xml schema
Siyana Slavova created AXIS2-5939:
-
Summary: Axis2 not parsing correctly query parameters after
upgrading xml schema
Key: AXIS2-5939
URL: https://issues.apache.org/jira/browse/AXIS2-5939
Project: Axis
Secure
Cookie not returned to WebServer
I'm accessing a WebService on an BEA Server from a Java client using
AXIS2 1.7.8
As can be seen in the SSL trace AXIS2 is not returning the secure
cookie (named '_WL_AUTHCOOKIE_JSESSIONID') to the se
