libwww-perl / libwww-perl/HTTP-Cookies
In some cases the HTTP::Cookies module does not delete cookies [rt.cpan.org #84712]
Open
Nobody has claimed this yet.
- Dominant language
- Perl
- Stars
- 4
- Forks
- 19
- PR merge metrics
- No merged PRs in 30d
Description
Migrated from rt.cpan.org#84712 (status was 'new')
Requestors:
- KNI@cpan.org
Attachments:
From kni@cpan.org on 2013-04-18 06:55:30:
Hi,
In some cases the HTTP::Cookies module does not delete cookies.
Here is the issue in detail:
- when the foo.com URL is requested the "Cookie_check=1" cookie is set
- then server redirects us to pass.foo.com
- while requesting pass.foo.com the "Cookie_check=" cookie is set
- then server redirects us to ok.foo.com
On each step the server displays the STDOUT cookie.
Please view the examples of requests for w3m browser and LWP client (client.pl):
> tail -n 3 /etc/hosts
127.0.0.1 foo.com
127.0.0.1 pass.foo.com
127.0.0.1 ok.foo.com
> perl server.pl
> w3m -dump http://foo.com:8080
Received cookie: Cookie_check=1
Received cookie: Cookie_check=
Hello
> perl client.pl
Hello
> perl server.pl
undef at server.pl line 23.
Cookie_check=1 at server.pl line 29.
undef at server.pl line 35.
======
undef at server.pl line 23.
Cookie_check=1 at server.pl line 29.
Cookie_check=1 at server.pl line 35.
======
Sincerely,
Nick Kostyria
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the attached client.pl and server.pl examples and reproduce the foo.com to pass.foo.com to ok.foo.com redirect sequence. Compare the HTTP::Cookies behavior with the displayed w3m and LWP outputs; done means the client no longer retains Cookie_check=1 after the empty cookie is set.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- perl
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100