On Thursday, November 2, 2017 at 8:15:31 AM UTC-7, Anthony wrote: > > On Thursday, November 2, 2017 at 12:19:14 AM UTC-4, Dave S wrote: >> >> >> >> On Wednesday, November 1, 2017 at 7:15:11 PM UTC-7, Anthony wrote: >>> >>> It's response.headers. >>> >> >> Indeed, but that isn't a sufficient correction. >> >> /dps >> >> >>> >>> Anthony >>> >>> On Wednesday, November 1, 2017 at 1:18:07 AM UTC-4, Dave S wrote: >>>> >>>> I wanted to set the refresh on a page according to how often an event >>>> is occurring, and so I tried adding this to my controller function: >>>> >>>> response.header["meta"]='http-equiv="refresh" content="30"' >>>> >>>> However, it doesn't seem to show up. I'm also not seeing the >>>> 'X-Powered-By' header that is set coming into my function, according to a >>>> print response.headers >>>> >>>> If I put that print statement in my view, the result is None. >>>> >>> > Note that putting a print statement in a view will have no effect. >
It makes the console a little more cluttered. > > Anyway, http-equiv goes inside a <meta> tag in the <head> section of the > HTML page -- it does not get sent as an HTTP response header as you are > doing. > > Anthony > Okay, I was confused. One belongs to the content, the other to the transfer, right? And "inspect-element"'s network tab does show the x-powered by and the ersatz-meta header. My goal is to compute a refresh rate based on how frequently the table gets updated (a matter of minutes in my case of interest). What's the best way to pass that to the browser? /dps -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
