-
1. Re: Is there a quick fix/workaround for wildfly sending "100-Continue" twice to the client
asimmahmood Jan 7, 2019 10:43 AM (in response to wshi123)Are requests being sent to your Wildfly server over HTTP or AJP? I remember having a lot of issues with the 100-continue header on Wildfly 8.2 and switching to HTTP stopped them. I never did find out the root cause of the issue. It may have been this, it may have been something else but it did go away when I upgraded to Wildfly 10. I used the switch in protocol as a temporary solution until I could upgrade. Hopefully this is of some help to you.
-
2. Re: Is there a quick fix/workaround for wildfly sending "100-Continue" twice to the client
wshi123 Jan 7, 2019 1:55 PM (in response to asimmahmood)Hi Asim,
Thank you for the response. But I think your solution won't apply to us since the client request should already be HTTP.
Thanks,
Wendy -
3. Re: Is there a quick fix/workaround for wildfly sending "100-Continue" twice to the client
jaikiran Jan 8, 2019 8:57 AM (in response to wshi123)The fix for that issue is this commit UNDERTOW-429 Make sure the continue response is not sent twice · undertow-io/undertow@8eceaf6 · GitHub
I guess, you could build undertow from source (choose the exact version that's used in your WildFly version) and apply this to it and use the new jar in your installation.
-
4. Re: Is there a quick fix/workaround for wildfly sending "100-Continue" twice to the client
wshi123 Jan 8, 2019 9:30 AM (in response to jaikiran)Thank you! I ended up doing something similar by applying the wildfly 8.2.1.Final patch from Downloads · WildFly, which contains the undertow update with the commit you mentioned. It went pretty smoothly so was a good solution to me.