> For the complete documentation index, see [llms.txt](https://lbxa.gitbook.io/waf/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://lbxa.gitbook.io/waf/journey/milestones/inspiration.md). # Inspiration Choosing the right project I began my research by exploring general firewall software before delving into [Web Application Firewalls](https://www.cloudflare.com/learning/ddos/glossary/web-application-firewall-waf/) (WAFs). One prominent discovery was an open-source WAF called [Naxsi](https://github.com/nbs-system/naxsi), based on NGINX, which piqued my interest. To understand more about the inner workings of firewalls, I delved into the [source code of UFW](https://code.launchpad.net/ufw), the Uncomplicated Firewall used in Debian Linux machines. To my surprise, it was predominantly written in Python, a choice that intrigued me given Python's latency issues. In my quest for a stack that combines type-safety with NGINX, I found Naxsi, which served as a valuable example. It was built as an NGINX module, aligning with my vision. However, I recognized that I had [much to learn](https://www.cloudflare.com/learning/ddos/glossary/web-application-firewall-waf/) about the principles of WAFs in this exciting journey. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://lbxa.gitbook.io/waf/journey/milestones/inspiration.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 `automate deployments from our CI pipeline` 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.