From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] Refresh http header
Date: Tue, 22 Apr 2014 14:14:32 +0000 [thread overview]
Message-ID: <20140322141432.eklhad@comcast.net> (raw)
> Refresh: 30;url=http://the-brannons.com/
Sure, but, this is I think exactly the same header I use for code 302.
I guess you're saying sometimes we get this header with code 200,
and are suppose to jump on that.
Well I'm not looking for that, I'm watching the codes first,
but I might be able to check for the header even on code 200.
Not sure if I should infer in this case code 301, 302 or 303.
I'll let you know.
Karl Dahlke
next reply other threads:[~2014-04-22 18:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-22 14:14 Karl Dahlke [this message]
2014-04-22 20:48 ` Adam Thompson
-- strict thread matches above, loose matches on Subject: below --
2014-04-22 14:08 Adam Thompson
2014-04-22 12:45 Karl Dahlke
2014-04-22 17:02 ` Chris Brannon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140322141432.eklhad@comcast.net \
--to=eklhad@comcast.net \
--cc=Edbrowse-dev@lists.the-brannons.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).