HTTP is a generic exception that is not tied to the web2py environment -- therefore it doesn't know about response and response.headers. It is typically used to abort the current request processing and return a response immediately, so you would often want to ignore any existing response.headers (otherwise, you would have to first clear response.headers before raising the exception).
Anthony On Friday, October 2, 2015 at 1:09:01 PM UTC-4, Kiran Subbaraman wrote: > > Anthony, > Thank you. That works. > I thought this behaviour would have been there by default... or any > idea, why not? > > ________________________________________ > Kiran Subbaraman > http://subbaraman.wordpress.com/about/ > > On Fri, 02-10-2015 7:07 PM, Anthony wrote: > > Should be: > > > > raise HTTP(404, **response.headers) > > > > Anthony > > > > -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
