Any planned support for HTMX

[cyeganeh01248]

My projects have been moving towards more HTMX based solutions. I noticed katana doesn't have great parsing for this yet. I was curious if there is anything on the radar for this.

[olearycrew]

For HTMX or any javascript frontend rendering framwork, you'll probably need to use headless mode - see https://github.com/projectdiscovery/katana?tab=readme-ov-file#crawling-mode

As noted in standard mode

without any javascript or DOM rendering, potentially missing post-dom-rendered endpoints or asynchronous endpoint calls that might happen in complex web applications

But Headless runs in a headless browser you should be able to use katana with it.

[cyeganeh01248]

I noticed it still doesnt register all the endpoints even in headless mode. In a test app I wrote up, it has a /, /static/styles.less, and a /test path. where the /test path is activated by htmx. It doesn't seem to get that endpoint despite turning on jsl, jc, or headless/system chrome.

[Mzack9999]

@crigger61 Thanks for opening this issue. Would it be possible to provide an example of the page which is not correctly parsed? Generally headless should be able to render all compatible javascript engines, and indirectly various endpoints are captured at runtime via headless. If the endpoints instead are triggered by some particular browser events (ex. hoovering with the mouse, clicking, etc) or user interaction, katana is probably not still able to do it autonomously, so the only option is implementing a custom parser that extract these info via static analysis.

[dogancanbakir]

Closing this due to inactivity.