Re: don't consider '?' as a special case in path

Hi,

On 10/31/07, Benoit Fouet <benoit.fouetpurplelabs.com> wrote:
>
> [1]
> http://lists.mplayerhq.hu/pipermail/ffmp
eg-user/2007-October/012171.html


Aha! On closer inspection, the old url_split() only strips
the ? in
hostnames, not in paths (so technically, it strips http://host?opt=val, but
not http://host/?opt=val). We
can go back to that behaviour but it sounds
really bad. Maybe I should fix udp.c / rtp.c to strip the
question mark off
the host manually. . Of
course, if this is how it's supposed to work,
I'll add it back, but I doubt it is.

(Isn't there another way to transfer options between
protocol handlers, like
a cleaner way?)

Ronald
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-develmplayerhq.hu
http://lists.mplayerhq.hu/mailman/listinfo/ffmpeg-devel

On Wed, Oct 31, 2007 at 08:05:32AM -0400, Ronald S. Bultje
wrote:
> Hi,
> 
> On 10/31/07, Benoit Fouet <benoit.fouetpurplelabs.com> wrote:
> >
> > [1]
> > http://lists.mplayerhq.hu/pipermail/ffmp
eg-user/2007-October/012171.html
> 
> 
> Aha! On closer inspection, the old url_split() only
strips the ? in
> hostnames, not in paths (so technically, it strips http://host?opt=val, but
> not http://host/?opt=val). We
can go back to that behaviour but it sounds
> really bad. Maybe I should fix udp.c / rtp.c to strip
the question mark off
> the host manually. . Of
course, if this is how it's supposed to work,
> I'll add it back, but I doubt it is.

Roughly speaking I think it _is_ supposed to work that way.
The host
can be terminated by a / or a ? or a #, but everything from
the host
termination onwards (except # and whatever follows it) is
part of the
path that must be passed to the server in the request.

Rich
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-develmplayerhq.hu
http://lists.mplayerhq.hu/mailman/listinfo/ffmpeg-devel