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.

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

Cookie processing problem related to applications running on 'localhost' with non-default port #1491

Closed
miherlosev opened this issue Feb 12, 2018 · 1 comment
Assignees
Labels
AREA: client STATE: Auto-locked Issues that were automatically locked by the Lock bot TYPE: bug
Milestone

Comments

@miherlosev
Copy link
Contributor

Steps to reproduce:
Click button 'XHR: Get cookie using ...' and observe 'XSRF-TOKEN=' message in browser console (if run site without proxy).
With proxy, the message does not show. It indicates that cookie sets incorrectly.

Files to reproduce

@miherlosev miherlosev changed the title Cookie processing problem related applications running on localhost with non-default port Cookie processing problem related to applications running on 'localhost' with non-default port Feb 12, 2018
@miherlosev miherlosev added this to the Sprint #10 milestone Feb 12, 2018
@miherlosev miherlosev modified the milestones: Sprint #10, Sprint #11 Mar 15, 2018
AndreyBelym pushed a commit to AndreyBelym/testcafe-hammerhead that referenced this issue Feb 28, 2019
…calhost' with non-default port` (close DevExpress#1491) (DevExpress#1563)

* fix `Cookie processing problem related to applications running on 'localhost' with non-default port`

* refactor default port omitting

* fix omitDefaultPort

* localhost/127.0.0.1 case

* non-default localhost/127.0.0.1 (http) case

* add location test for default port omitting

* requested changes

* rename test function

* add tests

* rename tests

* requested changes
@lock
Copy link

lock bot commented Mar 28, 2019

This thread has been automatically locked since it is closed and there has not been any recent activity. Please open a new issue for related bugs or feature requests. We recommend you ask TestCafe API, usage and configuration inquiries on StackOverflow.

@lock lock bot added the STATE: Auto-locked Issues that were automatically locked by the Lock bot label Mar 28, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Mar 28, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
AREA: client STATE: Auto-locked Issues that were automatically locked by the Lock bot TYPE: bug
Projects
None yet
Development

No branches or pull requests

2 participants