August 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-12375) Server returns 2 JSESSIONID cookies

by Nicolas NESMON (Jira)

[ https://issues.jboss.org/browse/WFLY-12375?page=com.atlassian.jira.plugin... ] Nicolas NESMON commented on WFLY-12375: --------------------------------------- Yes that' it. Its results in the creation of a session cookie (JSESSIONID or whatever session cookie name you set in web.xml) when session object does not exist. > Server returns 2 JSESSIONID cookies > ------------------------------------ > > Key: WFLY-12375 > URL: https://issues.jboss.org/browse/WFLY-12375 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 17.0.1.Final > Reporter: Nicolas NESMON > Assignee: Flavia Rainone > Priority: Major > Labels: COOKIES, JSESSIONID > > Please find below the source code of my simplified JAX-RS application: > {code:java} > @ApplicationPath("myApp") > public class Application extends javax.ws.rs.core.Application { > public Application() { > } > @Override > public Set<Object> getSingletons() { > return Collections.singleton(new HelloWorldResource()); > } > } > {code} > {code:java} > @Path("/") > @Produces(MediaType.TEXT_PLAIN) > public class HelloWorldResource { > @Context > private HttpServletRequest httpServletRequest; > @GET > public Response helloWorld() { > HttpSession session = this.httpServletRequest.getSession(false); > return Response.ok(session == null ? "Hello world" : "Bye bye world") > .cookie(new NewCookie("JSESSIONID", "id", "demo", null, null, -1, false)).build(); > } > } > {code} > When deploying this application in WF 17.0.1.Final and running following request: > {noformat} > GET http://localhost:8080/demo/myApp/ > Host: localhost:8080 > User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:68.0) Gecko/20100101 Firefox/68.0 > Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 > Accept-Language: fr,fr-FR;q=0.8,en-US;q=0.5,en;q=0.3 > Accept-Encoding: gzip, deflate > Connection: keep-alive > Upgrade-Insecure-Requests: 1 > Pragma: no-cache > Cache-Control: no-cache > Cookie: JSESSIONID=Hello => without this cookie, I only get the cookie I created. > {noformat} > I get following response > {noformat} > HTTP/1.1 200 OK > Connection: keep-alive > Set-Cookie: JSESSIONID=id;Version=1;Path=/demo > Set-Cookie: JSESSIONID=hello.vpi070236; path=/demo > Content-Type: text/plain;charset=UTF-8 > Content-Length: 11 > Date: Tue, 13 Aug 2019 23:28:15 GMT > {noformat} > As you may notice, there are 2 JSESSIONID cookies in the response: > * The one I was expecting with "id" value since I created it. > * Another one created by the server even if I did not ask for it since in my code I don't create no HTTP session. And by the way this JSESSIONID cookie is created but there no server side session created...weird > Any idea why this second JSESSIONID cookies is created by the server ? > Since my real application don't use HTTP session at all the workaround I found is to set session tracking mode to URL: > {noformat} > <web-app> > <session-config> > <tracking-mode>URL</tracking-mode> > </session-config> > </web-app> > {noformat} > Thanks -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4603) Replace Deployment --runtime-name option not working

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFCORE-4603?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFCORE-4603: ------------------------------------------ [~ehugonnet] [~yersan] A tangent to clean up as part of any work on this: https://github.com/wildfly/wildfly-core/blob/master/server/src/main/java/... That should be context.readResource(PathAddress.EMPTY_ADDRESS, false); as we don't want to read the entire model just to check for child names. > Replace Deployment --runtime-name option not working > ---------------------------------------------------- > > Key: WFCORE-4603 > URL: https://issues.jboss.org/browse/WFCORE-4603 > Project: WildFly Core > Issue Type: Bug > Affects Versions: 10.0.0.Beta4 > Environment: Red Hat JBoss Enterprise Application Platform (EAP) 7.2 CP 3. > Reporter: Emmanuel Hugonnet > Assignee: Emmanuel Hugonnet > Priority: Major > > The scenario is that, if you have a deployment to be switched by a new one, the runtime-name property doesn't work the way it should. See the sequence of the commands bellow: > [standalone@localhost:9990 /] deploy helloworld-rs.war > [standalone@localhost:9990 /] deploy helloworld-rs-second.war —disabled > [standalone@localhost:9990 /] :replace-deployment(name=helloworld-rs-second.war,to-replace=helloworld-rs.war,runtime-name=foo.war) > [standalone@localhost:9990 /] /deployment=helloworld-rs-second.war:read-resource > { > "outcome" => "success", > "result" => { > "content" => [{"hash" => bytes { > 0xfe, 0x24, 0x1f, 0xd3, 0x19, 0xa3, 0x72, 0xd4, > 0xc6, 0xa4, 0x48, 0xe7, 0x8b, 0x9c, 0xc1, 0xd4, > 0xc7, 0x17, 0xdf, 0xaa > }}], > "enabled" => false, > "name" => "helloworld-rs-second.war", > "owner" => undefined, > "persistent" => true, > "runtime-name" => "helloworld-rs-second.war", > "subdeployment" => undefined, > "subsystem" => { > "undertow" => undefined, > "ejb3" => undefined, > "logging" => undefined > } > } > } > Foo.war is not applied. Looks like it was ignored. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12375) Server returns 2 JSESSIONID cookies

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-12375?page=com.atlassian.jira.plugin... ] Brian Stansberry commented on WFLY-12375: ----------------------------------------- AIUI the suggested bug here is that the inclusion of a JSESSIONID cookie in the request is resulting in the creation of a session object when one doesn't exist. > Server returns 2 JSESSIONID cookies > ------------------------------------ > > Key: WFLY-12375 > URL: https://issues.jboss.org/browse/WFLY-12375 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 17.0.1.Final > Reporter: Nicolas NESMON > Assignee: Flavia Rainone > Priority: Major > Labels: COOKIES, JSESSIONID > > Please find below the source code of my simplified JAX-RS application: > {code:java} > @ApplicationPath("myApp") > public class Application extends javax.ws.rs.core.Application { > public Application() { > } > @Override > public Set<Object> getSingletons() { > return Collections.singleton(new HelloWorldResource()); > } > } > {code} > {code:java} > @Path("/") > @Produces(MediaType.TEXT_PLAIN) > public class HelloWorldResource { > @Context > private HttpServletRequest httpServletRequest; > @GET > public Response helloWorld() { > HttpSession session = this.httpServletRequest.getSession(false); > return Response.ok(session == null ? "Hello world" : "Bye bye world") > .cookie(new NewCookie("JSESSIONID", "id", "demo", null, null, -1, false)).build(); > } > } > {code} > When deploying this application in WF 17.0.1.Final and running following request: > {noformat} > GET http://localhost:8080/demo/myApp/ > Host: localhost:8080 > User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:68.0) Gecko/20100101 Firefox/68.0 > Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 > Accept-Language: fr,fr-FR;q=0.8,en-US;q=0.5,en;q=0.3 > Accept-Encoding: gzip, deflate > Connection: keep-alive > Upgrade-Insecure-Requests: 1 > Pragma: no-cache > Cache-Control: no-cache > Cookie: JSESSIONID=Hello => without this cookie, I only get the cookie I created. > {noformat} > I get following response > {noformat} > HTTP/1.1 200 OK > Connection: keep-alive > Set-Cookie: JSESSIONID=id;Version=1;Path=/demo > Set-Cookie: JSESSIONID=hello.vpi070236; path=/demo > Content-Type: text/plain;charset=UTF-8 > Content-Length: 11 > Date: Tue, 13 Aug 2019 23:28:15 GMT > {noformat} > As you may notice, there are 2 JSESSIONID cookies in the response: > * The one I was expecting with "id" value since I created it. > * Another one created by the server even if I did not ask for it since in my code I don't create no HTTP session. And by the way this JSESSIONID cookie is created but there no server side session created...weird > Any idea why this second JSESSIONID cookies is created by the server ? > Since my real application don't use HTTP session at all the workaround I found is to set session tracking mode to URL: > {noformat} > <web-app> > <session-config> > <tracking-mode>URL</tracking-mode> > </session-config> > </web-app> > {noformat} > Thanks -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12375) Server returns 2 JSESSIONID cookies

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-12375?page=com.atlassian.jira.plugin... ] Brian Stansberry reassigned WFLY-12375: --------------------------------------- Component/s: Web (Undertow) (was: EE) Assignee: Flavia Rainone (was: Brian Stansberry) > Server returns 2 JSESSIONID cookies > ------------------------------------ > > Key: WFLY-12375 > URL: https://issues.jboss.org/browse/WFLY-12375 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 17.0.1.Final > Reporter: Nicolas NESMON > Assignee: Flavia Rainone > Priority: Major > Labels: COOKIES, JSESSIONID > > Please find below the source code of my simplified JAX-RS application: > {code:java} > @ApplicationPath("myApp") > public class Application extends javax.ws.rs.core.Application { > public Application() { > } > @Override > public Set<Object> getSingletons() { > return Collections.singleton(new HelloWorldResource()); > } > } > {code} > {code:java} > @Path("/") > @Produces(MediaType.TEXT_PLAIN) > public class HelloWorldResource { > @Context > private HttpServletRequest httpServletRequest; > @GET > public Response helloWorld() { > HttpSession session = this.httpServletRequest.getSession(false); > return Response.ok(session == null ? "Hello world" : "Bye bye world") > .cookie(new NewCookie("JSESSIONID", "id", "demo", null, null, -1, false)).build(); > } > } > {code} > When deploying this application in WF 17.0.1.Final and running following request: > {noformat} > GET http://localhost:8080/demo/myApp/ > Host: localhost:8080 > User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:68.0) Gecko/20100101 Firefox/68.0 > Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 > Accept-Language: fr,fr-FR;q=0.8,en-US;q=0.5,en;q=0.3 > Accept-Encoding: gzip, deflate > Connection: keep-alive > Upgrade-Insecure-Requests: 1 > Pragma: no-cache > Cache-Control: no-cache > Cookie: JSESSIONID=Hello => without this cookie, I only get the cookie I created. > {noformat} > I get following response > {noformat} > HTTP/1.1 200 OK > Connection: keep-alive > Set-Cookie: JSESSIONID=id;Version=1;Path=/demo > Set-Cookie: JSESSIONID=hello.vpi070236; path=/demo > Content-Type: text/plain;charset=UTF-8 > Content-Length: 11 > Date: Tue, 13 Aug 2019 23:28:15 GMT > {noformat} > As you may notice, there are 2 JSESSIONID cookies in the response: > * The one I was expecting with "id" value since I created it. > * Another one created by the server even if I did not ask for it since in my code I don't create no HTTP session. And by the way this JSESSIONID cookie is created but there no server side session created...weird > Any idea why this second JSESSIONID cookies is created by the server ? > Since my real application don't use HTTP session at all the workaround I found is to set session tracking mode to URL: > {noformat} > <web-app> > <session-config> > <tracking-mode>URL</tracking-mode> > </session-config> > </web-app> > {noformat} > Thanks -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12225) Document missing discovery capabilities

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/WFLY-12225?page=com.atlassian.jira.plugin... ] Radoslav Husar reassigned WFLY-12225: ------------------------------------- Assignee: Paul Ferraro (was: Radoslav Husar) > Document missing discovery capabilities > --------------------------------------- > > Key: WFLY-12225 > URL: https://issues.jboss.org/browse/WFLY-12225 > Project: WildFly > Issue Type: Sub-task > Reporter: Radoslav Husar > Assignee: Paul Ferraro > Priority: Major > > namely https://github.com/wildfly/wildfly-capabilities/tree/master/org/wildfly/d... -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4602) Add support for DigestPasswordMapper to JDBC SecurityRealm

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/WFCORE-4602?page=com.atlassian.jira.plugi... ] Darran Lofthouse updated WFCORE-4602: ------------------------------------- Fix Version/s: (was: 11.0.0.Beta1) > Add support for DigestPasswordMapper to JDBC SecurityRealm > ---------------------------------------------------------- > > Key: WFCORE-4602 > URL: https://issues.jboss.org/browse/WFCORE-4602 > Project: WildFly Core > Issue Type: Feature Request > Components: Security > Reporter: Darran Lofthouse > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12220) Implement JGroups discovery protocol based on WildFly Discovery SPI

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/WFLY-12220?page=com.atlassian.jira.plugin... ] Radoslav Husar commented on WFLY-12220: --------------------------------------- AD https://github.com/wildfly/wildfly-proposals/pull/242 > Implement JGroups discovery protocol based on WildFly Discovery SPI > ------------------------------------------------------------------- > > Key: WFLY-12220 > URL: https://issues.jboss.org/browse/WFLY-12220 > Project: WildFly > Issue Type: Feature Request > Components: Clustering > Affects Versions: 17.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Major > > At the time of writing, the protocol can leverage the static discovery managed by the discovery subsystem essentially replacing TCPPING functionality. > As more discovery providers are implemented the protocol could leverage any discovery mechanism replacing cloud discovery protocols. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-926) Fix test_service_detail_with_destination_rule e2e test

by Filip Brychta (Jira)

[ https://issues.jboss.org/browse/SWSQE-926?page=com.atlassian.jira.plugin.... ] Filip Brychta commented on SWSQE-926: ------------------------------------- Sent https://github.com/kiali/kiali/pull/1338 > Fix test_service_detail_with_destination_rule e2e test > ------------------------------------------------------ > > Key: SWSQE-926 > URL: https://issues.jboss.org/browse/SWSQE-926 > Project: Kiali QE > Issue Type: Bug > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > Labels: automation > > The test is failing with Exception: Timed out waiting for destination rule deletion -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12375) Server returns 2 JSESSIONID cookies

by Nicolas NESMON (Jira)

[ https://issues.jboss.org/browse/WFLY-12375?page=com.atlassian.jira.plugin... ] Nicolas NESMON updated WFLY-12375: ---------------------------------- Issue Type: Bug (was: Enhancement) > Server returns 2 JSESSIONID cookies > ------------------------------------ > > Key: WFLY-12375 > URL: https://issues.jboss.org/browse/WFLY-12375 > Project: WildFly > Issue Type: Bug > Components: EE > Affects Versions: 17.0.1.Final > Reporter: Nicolas NESMON > Assignee: Brian Stansberry > Priority: Major > Labels: COOKIES, JSESSIONID > > Please find below the source code of my simplified JAX-RS application: > {code:java} > @ApplicationPath("myApp") > public class Application extends javax.ws.rs.core.Application { > public Application() { > } > @Override > public Set<Object> getSingletons() { > return Collections.singleton(new HelloWorldResource()); > } > } > {code} > {code:java} > @Path("/") > @Produces(MediaType.TEXT_PLAIN) > public class HelloWorldResource { > @Context > private HttpServletRequest httpServletRequest; > @GET > public Response helloWorld() { > HttpSession session = this.httpServletRequest.getSession(false); > return Response.ok(session == null ? "Hello world" : "Bye bye world") > .cookie(new NewCookie("JSESSIONID", "id", "demo", null, null, -1, false)).build(); > } > } > {code} > When deploying this application in WF 17.0.1.Final and running following request: > {noformat} > GET http://localhost:8080/demo/myApp/ > Host: localhost:8080 > User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:68.0) Gecko/20100101 Firefox/68.0 > Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 > Accept-Language: fr,fr-FR;q=0.8,en-US;q=0.5,en;q=0.3 > Accept-Encoding: gzip, deflate > Connection: keep-alive > Upgrade-Insecure-Requests: 1 > Pragma: no-cache > Cache-Control: no-cache > Cookie: JSESSIONID=Hello => without this cookie, I only get the cookie I created. > {noformat} > I get following response > {noformat} > HTTP/1.1 200 OK > Connection: keep-alive > Set-Cookie: JSESSIONID=id;Version=1;Path=/demo > Set-Cookie: JSESSIONID=hello.vpi070236; path=/demo > Content-Type: text/plain;charset=UTF-8 > Content-Length: 11 > Date: Tue, 13 Aug 2019 23:28:15 GMT > {noformat} > As you may notice, there are 2 JSESSIONID cookies in the response: > * The one I was expecting with "id" value since I created it. > * Another one created by the server even if I did not ask for it since in my code I don't create no HTTP session. And by the way this JSESSIONID cookie is created but there no server side session created...weird > Any idea why this second JSESSIONID cookies is created by the server ? > Since my real application don't use HTTP session at all the workaround I found is to set session tracking mode to URL: > {noformat} > <web-app> > <session-config> > <tracking-mode>URL</tracking-mode> > </session-config> > </web-app> > {noformat} > Thanks -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4243) Test Scenario: rule scenarios with maps of simple types are failing

by Daniele Zonca (Jira)

[ https://issues.jboss.org/browse/DROOLS-4243?page=com.atlassian.jira.plugi... ] Daniele Zonca reassigned DROOLS-4243: ------------------------------------- Assignee: Lance Leverich (was: Daniele Zonca) > Test Scenario: rule scenarios with maps of simple types are failing > ------------------------------------------------------------------- > > Key: DROOLS-4243 > URL: https://issues.jboss.org/browse/DROOLS-4243 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Lance Leverich > Priority: Critical > Labels: ScenarioSimulation, rhpam74releasenote > > Create a map of simple type as value (i.e. Map<String, String>) and try to use it -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira August 2019