[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#637225: marked as done (URL encoding of some RFC3986 unreserved characters (e.g., tilde) can be a problem for some webservers)

Your message dated Tue, 11 Aug 2015 15:52:31 +0200
with message-id <20150811135230.GA4843@crossbow>
and subject line Re: URL encoding of some RFC3986 unreserved characters (e.g., tilde) can be a problem for some webservers
has caused the Debian Bug report #637225,
regarding URL encoding of some RFC3986 unreserved characters (e.g., tilde) can be a problem for some webservers
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
637225: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=637225
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: apt
Severity: normal
Version: 0.8.10.3+squeeze1
Tags: patch

Unreserved characters (see http://tools.ietf.org/html/rfc3986#section-2.3) never
need to be percent-encoded.   This even can cause problems for some webservers,
e.g. GoogleApp's Engine when it serves static files:

$ HEAD -d 'http://localhost:8080/debian/pool/main/m/monit/monit_5.2.5-2%7ebpo60+2_amd64.deb'
404 Not Found
$ HEAD -d 'http://localhost:8080/debian/pool/main/m/monit/monit_5.2.5-2~bpo60+2_amd64.deb'
200 OK

Attached simple patch fix this problem for the "tilde" character.

Attachment: patch-tilde.diff
Description: Binary data


--- End Message ---
--- Begin Message --- 
Hi,

On Tue, Aug 09, 2011 at 08:56:27PM +0400, Sergey B Kirpichev wrote:
> Unreserved characters (see http://tools.ietf.org/html/rfc3986#section-2.3) never
> need to be percent-encoded.   This even can cause problems for some webservers,
> e.g. GoogleApp's Engine when it serves static files:

The problem is that QuoteString() is explicitely requested (via the Bad
parameter) to encode the '~' (as well as a few others which should have
been allowed) in method/http.cc since 1998.

This is done for stuff like S3 which doesn't work if you don't do it, so
we are stuck between a rock and a hard place as either this or the other
is breaking and currently it seems that encoding ~ unbreaks more of the web
than not encoding it does.

A solution might be to provide 'specialized' methods you can use instead of
http, like s3://, googleapps://, … which do the funky "similar to http, but not
quite" protocol all these different webservers use – or we could force all
webservers to be sane… (sorry, I couldn't resist).

Either way, this is outside of possibilities of this bugreport and I therefore
close it.


Best regards

David Kalnischkies

Attachment: signature.asc
Description: Digital signature


--- End Message ---
Reply to: