Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window)
Runwar has support for many of the undertow options, but it would also be handy to have a generic approach for any edge case options or new options that a user needs to tap into that we don't have first-class support for yet.
New server.json and config server default settings added:
server set runwar.undertowOptions.ALLOW_UNESCAPED_CHARACTERS_IN_URL=true
server set runwar.XNIOOptions.WORKER_NAME=myWorker
Brad WoodOctober 30, 2019 at 7:52 PM
Edited
@Miguel Mathus So this is what we were testing today. For the sake of documentation, the two new runwar args are:
xnio-options
undertow-options
Settings like IO or worker threads are XNIO options but settings like ALLOW_UNESCAPED_CHARACTERS_IN_URL are undertow options
An example of using the setting above in a server is
server set runwar.args=--undertow-options=ALLOW_UNESCAPED_CHARACTERS_IN_URL=true
Note it needs to be added as a runwar arg, not a jvm arg. This changes the position in the list of args that it gets added in so runwar picks it up instead of java itself.
Stephany MongeSeptember 2, 2019 at 5:41 PM
Complete Functional Testing is pending from @Miguel Mathus
Original runwar Issue #148
Runwar has support for many of the undertow options, but it would also be handy to have a generic approach for any edge case options or new options that a user needs to tap into that we don't have first-class support for yet.
http://undertow.io/undertow-docs/undertow-docs-2.0.0/index.html#options