Looks like Undertow 1.1.1.Final didn't make Wildfly 8.2 cut. Will there
even be a Wildfly 8.2.1?
On 12/1/2014 7:18 PM, Stuart Douglas wrote:
I have cut 1.1.1.Final
Stuart
----- Original Message -----
> From: "Bill Burke" <bburke(a)redhat.com>
> To: "Stuart Douglas" <sdouglas(a)redhat.com>
> Cc: undertow-dev(a)lists.jboss.org
> Sent: Tuesday, 2 December, 2014 2:13:48 AM
> Subject: Re: [undertow-dev] req.authenticate() problems 1.1.0
>
> 1.1.1 or 1.2.x release incoming? We're doing a keycloak release with
> the proxy this week, just wondering if I should delay if undertow is
> incoming so I can upgrade the proxy distro.
>
> On 11/25/2014 3:41 PM, Stuart Douglas wrote:
>> This should be fixed upstream, I will do a 1.1.1 release shortly, so if you
>> discover any other issues let me know and I will try and get them into
>> this release.
>>
>> Stuart
>>
>> ----- Original Message -----
>>> From: "Stuart Douglas" <sdouglas(a)redhat.com>
>>> To: "Bill Burke" <bburke(a)redhat.com>
>>> Cc: undertow-dev(a)lists.jboss.org
>>> Sent: Wednesday, 26 November, 2014 6:19:41 AM
>>> Subject: Re: [undertow-dev] req.authenticate() problems 1.1.0
>>>
>>> Is the code up on Github anywhere? If so I can take a look.
>>>
>>> Stuart
>>>
>>> ----- Original Message -----
>>>> From: "Bill Burke" <bburke(a)redhat.com>
>>>> To: undertow-dev(a)lists.jboss.org
>>>> Sent: Wednesday, 26 November, 2014 3:30:41 AM
>>>> Subject: [undertow-dev] req.authenticate() problems 1.1.0
>>>>
>>>> When upgrading from Undertow 1.0.15 to 1.1.0 our
>>>> HttpServleRequest.authenticate() unit test is failing. An exception is
>>>> being thrown in HttpServletRequestImpl.authenticate() line 416.
>>>>
>>>> Our auth mechanism is being called correctly. It sets the status code
>>>> (302) and the Location header within a challenge object. It looks like
>>>> exchange.isResponseStarted() is returning false even though my challenge
>>>> object is setting up the resposne correctly. Am I supposed to call
>>>> exchange.endExchange() or something within my Challenge object? I tried
>>>> doing that, but Undertow is now spitting out exception messages:
>>>>
>>>> java.lang.IllegalStateException: UT000002: The response has already been
>>>> started
>>>> at
>>>>
io.undertow.server.HttpServerExchange.setResponseCode(HttpServerExchange.java:1246)
>>>> at
>>>>
io.undertow.security.impl.SecurityContextImpl$ChallengeSender.transition(SecurityContextImpl.java:355)
>>>> at
>>>>
io.undertow.security.impl.SecurityContextImpl$ChallengeSender.transition(SecurityContextImpl.java:349)
>>>> at
>>>>
io.undertow.security.impl.SecurityContextImpl$ChallengeSender.transition(SecurityContextImpl.java:349)
>>>> at
>>>>
io.undertow.security.impl.SecurityContextImpl$ChallengeSender.access$300(SecurityContextImpl.java:314)
>>>> at
>>>>
io.undertow.security.impl.SecurityContextImpl.sendChallenges(SecurityContextImpl.java:135)
>>>> at
>>>>
io.undertow.security.impl.SecurityContextImpl.authTransition(SecurityContextImpl.java:109)
>>>> at
>>>>
io.undertow.security.impl.SecurityContextImpl.authenticate(SecurityContextImpl.java:99)
>>>> at
>>>>
io.undertow.servlet.spec.HttpServletRequestImpl.authenticate(HttpServletRequestImpl.java:404)
>>>>
>>>>
>>>> --
>>>> Bill Burke
>>>> JBoss, a division of Red Hat
>>>>
http://bill.burkecentral.com
>>>> _______________________________________________
>>>> undertow-dev mailing list
>>>> undertow-dev(a)lists.jboss.org
>>>>
https://lists.jboss.org/mailman/listinfo/undertow-dev
>>>>
>>> _______________________________________________
>>> undertow-dev mailing list
>>> undertow-dev(a)lists.jboss.org
>>>
https://lists.jboss.org/mailman/listinfo/undertow-dev
>>>
>
> --
> Bill Burke
> JBoss, a division of Red Hat
>
http://bill.burkecentral.com
>