Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Cookie problems with session tracking turned on #15

Open
zapbot opened this issue Jun 4, 2015 · 5 comments
Open

Cookie problems with session tracking turned on #15

zapbot opened this issue Jun 4, 2015 · 5 comments
Labels
Priority-Medium Type-Defect

Comments

@zapbot
Copy link
Contributor

zapbot commented Jun 4, 2015 

David has reported an issue with ZAP supplying multiple session cookies when session
tracking is turned on.
The target application didnt like it and he has unable to login.
Full details have been supplied via email.

Original issue reported on code.google.com by psiinon on 2010-11-04 09:35:48
@zapbot
Copy link
Contributor Author

zapbot commented Jun 4, 2015 

Closing - Stale.

Original issue reported on code.google.com by kingthorin on 2014-05-15 20:28:26

@zapbot
Copy link
Contributor Author

zapbot commented Jun 4, 2015 

Not really the issue is still present and easily reproducible ;)

Original issue reported on code.google.com by THC202 on 2014-05-16 00:46:32

@zapbot
Copy link
Contributor Author

zapbot commented Jun 4, 2015 

We really need to decide how session tracking fits in with things like the active session
and scan / spider as...
Does it still make sense to support this?
When would people use this instead of the other options.
We need to rationalize our approach here

Original issue reported on code.google.com by psiinon on 2014-05-16 09:19:59

@zapbot
Copy link
Contributor Author

zapbot commented Jun 4, 2015 

Fair enough, want me to re-open?

Original issue reported on code.google.com by kingthorin on 2014-05-16 21:26:50

@zapbot
Copy link
Contributor Author

zapbot commented Jun 4, 2015 

I've marked it as "Accepted" again.

There is other issue related to the "Session Tracking" option (Issue 1161).

Original issue reported on code.google.com by THC202 on 2014-05-16 23:13:50

kingthorin added a commit to kingthorin/zaproxy that referenced this issue Nov 1, 2016
@kingthorin
Custom Pages Initial zaproxy#15
9adb114 
CustomPage and DefaultCustomPage javadoc additions.
kingthorin added a commit to kingthorin/zaproxy that referenced this issue Nov 13, 2016
@kingthorin
Custom Pages Initial zaproxy#15
fa15bd0 
CustomPage and DefaultCustomPage javadoc additions.
kingthorin added a commit to kingthorin/zaproxy that referenced this issue Nov 17, 2016
@kingthorin
Custom Pages Initial zaproxy#15
1d4631b 
CustomPage and DefaultCustomPage javadoc additions.
kingthorin added a commit to kingthorin/zaproxy that referenced this issue Jan 20, 2017
@kingthorin
Custom Pages Initial zaproxy#15
77de90f 
CustomPage and DefaultCustomPage javadoc additions.
kingthorin added a commit to kingthorin/zaproxy that referenced this issue Jan 27, 2017
@kingthorin
Custom Pages Initial zaproxy#15
9759f50 
CustomPage and DefaultCustomPage javadoc additions.
kingthorin added a commit to kingthorin/zaproxy that referenced this issue Apr 9, 2017
@kingthorin
Custom Pages Initial zaproxy#15
98920f9 
CustomPage and DefaultCustomPage javadoc additions.
@truesamurai truesamurai mentioned this issue Aug 16, 2019
Closed
psiinon added a commit to psiinon/zaproxy that referenced this issue Jun 24, 2020
@psiinon
Merge pull request zaproxy#15 from thc202/crowdin-api-update
2c3915f 
Update Crowdin library for latest API changes
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Priority-Medium Type-Defect
Milestone
No milestone
Development

No branches or pull requests
1 participant
@zapbot