Replies: 1 comment 2 replies
-
semicolons are not supported as the web has rarely ever used them in URLs in the past 20 years. with proper HTML escaping no one should ever notice the escaped form. I would not expect a patch to be accepted. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I hope this isn't a foolish question or that I've missed a baseline change in standards but I personally prefer the semicolon to the ampersand for URI query strings. I find it easier to read, to type, and especially like to see them in HTML in place of &s.
I'm a mojo n00b but it appears only the ampersand is supported. Am I wrong? Is there a reason? Would a patch to include the semicolon as an acceptable optional delimiter be accepted? Are there implications in URI construction there? As with the need to set it globally like $URI::DEFAULT_QUERY_FORM_DELIMITER in URI:: space.
Thank you!
Beta Was this translation helpful? Give feedback.
All reactions