Blog

Luis Majano

October 15, 2008

Spread the word


Share your thoughts

Matt Quackenbush submitted this unusual behavior a few days ago and I was finally able to reproduce and fix today. Here is his excerpt:

If I browse to http://localhost/myApp/index.cfm/main/dspHome (or any other explicitly-called event), everything is good to go. However, if I browse to http://localhost/myApp/ or http://localhost/myApp/index.cfm, an exception is thrown that says: The event handler: index.cfm.dspHome is not valid registered event.

The problem was the cleaning of the path info and cgi script name in the ses interceptor. The fix is on SVN and also attached to this post. It is a single file ses.cfc Just grab it and overwrite the original ses.cfc interceptor in your coldbox installation, which can be found at:

/coldbox/system/interceptors/ses.cfc

That's it folks. This bug has also been registered and will be available on the daily builds, SVN and the next major milestone. I will also be updating the 2.5.1 build with the updated file.

Add Your Comment

(1)

Dec 23, 2007 02:13:37 UTC

by Matt Quackenbush

Awesome Luis! Thanks for the quick fix! It's rockin' and rollin' now!

Recent Entries

MatchBox and WebAssembly: Running BoxLang in the Browser and at the Edge

MatchBox and WebAssembly: Running BoxLang in the Browser and at the Edge

The MatchBox open beta is live at https://boxlang.ortusbooks.com/boxlang-framework/matchbox, and it brings something genuinely new to the BoxLang ecosystem: a path into WebAssembly.

That means BoxLang code can now move into browser applications, static-site deployments, edge runtimes, and WASI-style containers - without requiring a JVM. The feature is still beta, but the core direction is already useful: write BoxLang, compile it with MatchBox, and ship the generated WASM artifact to wherever a small portable runtime makes sense.

Jacob Beers
Jacob Beers
June 04, 2026