Url with underscore in subdomain is not working
See original GitHub issueCurrent behavior:
We have an project environment like this: https://opt_in_opt_out.bzr.project.independer.nl
If I start the runner and select any script the page stays empty.
Desired behavior:
Just run the scripts just like normal
Steps to reproduce: (app code and test code)
Make a project environment with _
(underscores) in it.
Run a script against it
Versions
Cypress: 3.0.1 Windows 7 Chrome 74.0.3729.169
Issue Analytics
- State:
- Created 4 years ago
- Reactions:7
- Comments:14 (5 by maintainers)
Top Results From Across the Web
Can (domain name) subdomains have an underscore "_"
URLs can't have underscores. A URL is always a FQDN, it's not a host name. A FQDN can have an empty host name,...
Read more >iOS 14 Conflict with Underscores in Subdomain
iOS 14 no longer supports underscores in subdomains / hostnames. · Any form with an underscore in the subdomain that is being shared...
Read more >Underscores Not Allowed in Domain Names - SSL.com
(Recommended) If possible, change the name of the subdomain so that it no longer contains underscores (e.g. change. sub_domain.example.com · If ...
Read more >Underscores not allowed in FQDNs - DigiCert.com
As of October 1, 2018, DigiCert no longer issues public certificates for domains and subdomains that contain underscores ( _ ). This applies...
Read more >Underscore in subdomain fails - Help
Ok, I think we have a problem with different description of what we have here - a hostname or a DNS domain name....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@Niceplace The Stackoverflow question and the RFC referenced in it RFC3986#section-3.1 refers to the
scheme
part of the URL.So my understanding is that it’s perfectly legal for the rest of the URL to can contain an
_
as explained in here RFC2181#section-11So this looks like a bug in Cypress.
@MtDalPizzol I think that is just the error message being incorrectly handled as markdown:
__cypress__
-> cypress