Ernst has just posted his code for an ssl interceptor he just created. It looks awesome so take a look for yourself.
Blog
Recent Entries
BoxLang AI 3.4.0: Gateways, Human-in-the-Loop, and a Full Security Stack
BoxLang AI 3.4.0 is one of the biggest releases in the module's history, and it is built around a single theme: trust. Every agent you ship eventually needs a human to step in, and every agent that reads untrusted content is a target for prompt injection. This release gives you both a proper answer.
Luis Majano
Luis Majano
September
01,
2026
Ortus & BoxLang August Recap 2026
Product Releases & Tools
-
bx-toml: Native TOML Support for BoxLang
This post introduces bx-toml 1.0.0, a new BoxLang module providing native TOML parsing and serialization. It ad...
Victor Campos
Victor Campos
August
31,
2026
Add Your Comment
(4)
Jan 19, 2008 23:50:35 UTC
by Rob Gonda
It's missing some functionality ... how does it know which event has to be secured? It should secure only specific events, and force unsecured requests for the rest. something like
if not isSsl and requireSll then cflocate to https
if isSsl and not requireSll then cflocate to http
Jan 19, 2008 23:54:53 UTC
by Luis Majano
That is up to Ernst, but I think its a good start.
Jan 21, 2008 16:01:48 UTC
by Ernst van der Linden
Rob you're right. We could implement that. Just make a list of allowed events without SSL as a property in interceptor xml definition and then check with event.getCurrentEvent() if we need SSL.
I will take a look and keep you informed.
Jan 21, 2008 17:47:57 UTC
by Ernst van der Linden
Rob, I made in new blog entry. The SSL interceptor now supports SSL for specific events.
Comments are welcome!