We're sorry, but something went wrong

Lasse Laursen laursen at oxygen.net
Wed Oct 2 15:08:00 UTC 2013

That sounds like a RoR app acting up and not the nginx server itself.


On Oct 2, 2013, at 4:28 PM, Scott Ribe <scott_ribe at elevated-dev.com> wrote:

> So I'm in the early stages of rolling out a system to production, and a few app errors are cropping up that didn't get caught in testing, and it occurs to me: it would be nice if the default "we're sorry, but something went wrong" error page could include a timestamp.
> -- 
> Scott Ribe
> scott_ribe at elevated-dev.com
> http://www.elevated-dev.com/
> (303) 722-0567 voice
> _______________________________________________
> nginx mailing list
> nginx at nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 841 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20131002/67156f81/attachment.bin>

More information about the nginx mailing list