Re: [apps-discuss] character repertoire for fragment identifiers

[<[e-mail]>]

> From: Sam Ruby
> 
> Again, it is my hope/expectation that by year end every single one of 
> the parsers that I have looked out (with the possible/probable exception 
> of Perl) will NOT percent encode fragments.
> … 

> 
> I have published a lot of test values that I am looking for people to 
> work through with me.  Cooperation amongst browser vendors in this 
> effort is increasing.  I have yet to find anybody on this list willing 
> to look at this data.



I have looked at the test data.  Specifically I have looked at the comparisons between the .NET framework (csharp) URI parser and the reference implementation.


I’m not sure how you ever expect to obtain a consistent result between a library that returns errors along with a parsed result and one that throws an exception and aborts parsing upon encountering an error.  Is it your expectation that the .Net framework stops throwing exceptions when URI parsing?


Also, regarding escaping of fragment identifiers, in your csharp test program you use Uri.Fragment, which is explicitly documented to return an escaped fragment.  If the developer does not wish the fragment to be escaped then they are free to use,



Uri.GetComponents(UriComponents.Fragment, UriFormat.Unescaped)


Different languages do things in different ways.  Trying get every URL parsing library to behave identically just feels like an ocean boiling exercise. 


Darrel