search

Balzanka / guava-libraries

Automatically exported from code.google.com/p/guava-libraries
Apache License 2.0
0 stars 0 forks source link

urlFragmentEscaper #1303

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
(another post-Escaper item)

I'm somewhat confident that we'll want to do this. We have at least 3 people 
internally who are trying to do it now. My main reservation is that all our URL 
escapers seem to be used more frequently to encode query parameters than they 
are for their intended purposes. Every time that we add a new one, we're 
increasing the overhead to our users and, I fear, encouraging them to pick one 
at random. Probably, though, I'll just say "tough" and go with it. People who 
are doing the right thing ought to get support from the library, and we'll do 
our best to point users loudly in the right direction.

Note that our uriQueryStringEscaper doesn't quite match the encoding for 
fragments (or query strings as a whole), as it encodes &, +, and =.

Original issue reported on code.google.com by cpov...@google.com on 26 Feb 2013 at 7:50

GoogleCodeExporter commented 9 years ago 
I think it is useful to have a special escaper for fragments given their 
prevalence in modern web apps.

Original comment by chr...@google.com on 1 Aug 2013 at 2:02

GoogleCodeExporter commented 9 years ago 
http://code.google.com/p/guava-libraries/source/detail?r=6e21d471651c79e18212060
5f3f795887d0e03a4

Original comment by cpov...@google.com on 8 Aug 2013 at 3:49

GoogleCodeExporter commented 9 years ago 
This issue has been migrated to GitHub.

It can be found at https://github.com/google/guava/issues/<id>

Original comment by cgdecker@google.com on 1 Nov 2014 at 4:13

GoogleCodeExporter commented 9 years ago

Original comment by cgdecker@google.com on 3 Nov 2014 at 9:08