<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Oct 25, 2016, at 12:50 PM, Saagar Jha via swift-evolution &lt;<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>&gt; wrote:</div><br class="Apple-interchange-newline"><div class="">This is expected behavior. The semicolon character is reserved in URLs, and it requires escaping if it is used. <br class=""></div></blockquote><div><br class=""></div>This is not accurate:</div><div><br class=""></div><div>"If data for a URI component would conflict with a reserved</div><div class="">&nbsp; &nbsp;character's purpose as a delimiter, then the conflicting data must be</div><div class="">&nbsp; &nbsp;percent-encoded before the URI is formed.”</div><div class=""><br class=""></div><div class="">HTTP URIs do not define a semantic for the use of a semicolon within a path segment, so semicolons are legal to have unescaped.</div><div class=""><br class=""></div><div class="">Likewise, if there was meaning to having a semicolon within a path segment for this kind of URI, you would have broken the meaning of that URI by encoding it - in the original URI it would be a separator, while in the output URI it would be part of the path segment text.</div><div class=""><br class=""></div><div class="">-DW</div><div class=""><br class=""></div><div><blockquote type="cite" class=""><div class=""><div class="gmail_quote"><div dir="ltr" class="">On Tue, Oct 25, 2016 at 12:05 Cao, Jiannan via swift-evolution &lt;<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>&gt; wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br class="gmail_msg">
<a href="http://host/book;id=1/page;2/" rel="noreferrer" class="gmail_msg" target="_blank">http://host/book;id=1/page;2/</a><br class="gmail_msg">
<br class="gmail_msg">
this URL is a valid URL, but URLComponents will ruin it with %3B<br class="gmail_msg">
<a href="http://host/book%3Bid=1/page%3B2/" rel="noreferrer" class="gmail_msg" target="_blank">http://host/book%3Bid=1/page%3B2/</a><br class="gmail_msg">
<br class="gmail_msg">
Since Swift Server is coming out, this bug should be solved.<br class="gmail_msg">
<br class="gmail_msg">
<br class="gmail_msg">
_______________________________________________<br class="gmail_msg">
swift-evolution mailing list<br class="gmail_msg">
<a href="mailto:swift-evolution@swift.org" class="gmail_msg" target="_blank">swift-evolution@swift.org</a><br class="gmail_msg">
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" class="gmail_msg" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br class="gmail_msg">
</blockquote></div>
_______________________________________________<br class="">swift-evolution mailing list<br class=""><a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a><br class="">https://lists.swift.org/mailman/listinfo/swift-evolution<br class=""></div></blockquote></div><br class=""></body></html>