Blog

Luis Majano

October 15, 2008

Spread the word


Share your thoughts

This is a question for you to answer. ColdBox supports the mode of being in debug mode or not. It does so, by placing a cookie on your browser so you can see the debugging panel only with that cookie set. The question is, how long should that cookie live? What should the expiration time be? Any suggestions?

Add Your Comment

(4)

Feb 23, 2007 03:50:04 UTC

by Sana

Hi Luis, I think 30 minutes, as sessions default expiry is 30 minutes, so this cookie should be 30 minutes expiry time.

Feb 23, 2007 07:29:14 UTC

by Dan Wilson

Luis, Perhaps it could be left up to the user to clear the cookie when they have finished the debugging? A link or a special URL perhaps to clear the cookie? Dan

Feb 23, 2007 10:00:43 UTC

by reuben

I agree with Sana that the time out for a cookie should be defaulted to the session timeout. If you are working constantly on the site, the debug will last beyond 30 minutes. The big issue is that if you stop work and come back to the site, you don't always want debug still enabled. I think having it auto expire is a good thing.

Feb 23, 2007 10:24:47 UTC

by Luis Majano

Dan, You can clear the cookie by just setting debugmode=false once you are done. But we all know that sometimes we are lazy and basically forget, like 90 year old brians!! So an automatic timeout, would allow security and also peace of mind. I think 30 minutes is reasonable. Any more suggestions.

Recent Entries

BoxLang AI v2.1.0: Enterprise-Grade Multi-Tenancy, OpenSearch, and AWS Bedrock Support

BoxLang AI v2.1.0: Enterprise-Grade Multi-Tenancy, OpenSearch, and AWS Bedrock Support

We're excited to announce BoxLang AI v2.1.0, a major release that brings enterprise-grade features to your AI-powered applications. This release focuses on production readiness with multi-tenant usage tracking, scalable OpenSearch vector memory, complete AWS Bedrock integration, and simplified provider configuration.

Luis Majano
Luis Majano
February 04, 2026