> For the complete documentation index, see [llms.txt](https://commandbox.ortusbooks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://commandbox.ortusbooks.com/5.0.0/embedded-server/configuring-your-server/undertow-options.md). # Undertow Options CommandBox uses JBoss Undertow to power it's lightweight servlet containers. Undertow also powers JBoss Wildfly and has a lot of configurable options, not all of which have first-class CommandBox settings. These low-level settings come in two different categories: * **Undertow Options** - Settings that apply to the servlet and web server aspects of Undertow * **XNIO Options** - Part of the underlying XNIO library which powers all low-level I/O in undertow ## Undertow Options Undertow has its own set of options which can be found here: {% embed url="" %} To set an XNIO option that CommandBox doesn't already expose with a first-class setting, you can set them into your `server.json` like so: ```bash server set runwar.undertowOptions.ALLOW_UNESCAPED_CHARACTERS_IN_URL=true ``` You can also set global XNIO objects that will apply to all servers. Global options will be appended to server-level options. ```bash config set server.defaults.runwar.undertowOptions.WORKER_NAME=myWorker ``` ## XNIO Options XNIO (which is a refined version of NIO (Non-blocking I/O) has its own set of options that apply to the low level network transport functions it provides. You can find the full set of XNIO options here: {% embed url="" %} To set an XNIO option that CommandBox doesn't already expose with a first-class setting, you can set them into your `server.json` like so: ```bash server set runwar.XNIOOptions.WORKER_NAME=myWorker ``` You can also set global XNIO objects that will apply to all servers. Global options will be appended to server-level options. ```bash config set server.defaults.runwar.XNIOOptions.WORKER_NAME=myWorker ``` --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://commandbox.ortusbooks.com/5.0.0/embedded-server/configuring-your-server/undertow-options.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.