edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Tyler Spivey <tspivey@pcdesk.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] Cookies
Date: Wed, 6 Jan 2016 20:30:24 -0800	[thread overview]
Message-ID: <568DE9E0.6020009@pcdesk.net> (raw)

Here we go.
Browse this page, which is a simple php script I set up:
http://allinaccess.com/cookie.php
The first time you go there, it should set the cookie with an expiration
time of one year.
Set-Cookie: test=ok; expires=Thu, 05-Jan-2017 18:21:29 GMT
So far so good; the page says "test set".
Refresh with rf, we send the cookie.
Cookie: test=ok
Quit Edbrowse and look at the jar.
It's there.
allinaccess.com>FALSE>/>FALSE>1483640489>test>ok
Start it back up,
db4
b http://allinaccess.com/cookie.php
No cookie gets sent.
Is this a bug in the browser, or my script?
If we test with a clean Firefox profile, going to the page sets the
cookie the first time, and says ok the second time after restarting the
browser.

             reply	other threads:[~2016-01-07  4:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-07  4:30 Tyler Spivey [this message]
2016-01-07 12:58 ` 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=568DE9E0.6020009@pcdesk.net \
    --to=tspivey@pcdesk.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).