-
Notifications
You must be signed in to change notification settings - Fork 24
Conversation
Is there anything I can do to get it merged? Thank you. |
I'm not sure what this change buys us. Case insensitivity here simply means that, for purposes of equivalency, different cases are the same. It does not mean that there MUST be a single representation of the host name. Casting it to lower case has some ramifications, particularly when we consider unicode domain names, as calling As such, I'm closing this at this point. If developers need to do URI hostname comparisons, they should ensure they use case-insensitive comparison operations. |
If we check |
Hmmm... I swear I checked that yesterday, but somehow I must have missed the Re-opening. I still maintain it could be considered a BC break, but we'll do another minor release to call out the change, as it does make it more consistent. |
Thanks, @samsonasik! Merged to develop for an immediate 2.7.0 release, with a CHANGELOG entry calling out the change in behavior. |
@weierophinney you was right with breakage. Simple case from Magento 2.3. Host is not always domain or IP address. When we using docker we can call host via container names. Example:
When we call
So If anyone ( like me ) using aliases on magento then this patch break eg. Varnish Purge request. |
Based on https://tools.ietf.org/html/rfc3986#section-3.2.2 , the host subcomponent is case-insensitive, so the "www.EXAMPLE.com" is same with "www.example.com". I think it should be normalized to lowercase within
Uri::setHost()
call.