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

Location wrapper returns case-sensitivity port, hostname and protocol in the href field (T272552) #1

Closed
churkin opened this issue Jul 30, 2015 · 7 comments
Labels
AREA: client STATE: Auto-locked Issues that were automatically locked by the Lock bot TYPE: bug

Comments

@churkin
Copy link
Contributor

churkin commented Jul 30, 2015

Proxied page - http://localhost:1401/!2/http://Example.com/.

location.href should returns http://example.com instead of http://Example.com

@inikulin
Copy link
Contributor

Is this behavior consistent across browsers? Can't find it in URL spec (Location interface is inherited from URLUtils per living DOM spechttps://html.spec.whatwg.org/multipage/browsers.html#location).

@churkin
Copy link
Contributor Author

churkin commented Jul 30, 2015

Browser sends requests with host, port, protocol in the lower case

@inikulin
Copy link
Contributor

All browsers?

@churkin
Copy link
Contributor Author

churkin commented Jul 30, 2015

I have checked IE, FF, Chrome

@inikulin
Copy link
Contributor

OK then

@churkin churkin changed the title Location wrapper returns case-sensitivity port, hostname and protocol (T272552) Location wrapper returns case-sensitivity port, hostname and protocol in the href field (T272552) Jul 30, 2015
churkin pushed a commit to churkin/testcafe-hammerhead that referenced this issue Jul 30, 2015
testcafe-build-bot pushed a commit to testcafe-build-bot/testcafe-hammerhead that referenced this issue Aug 17, 2015
@inikulin
Copy link
Contributor

fixed via 76d5232

@lock
Copy link

lock bot commented Mar 29, 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 29, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Mar 29, 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