logo       

Re: Re: [xine-cvs] CVS: xine-vcdnav/doc cd-info.txt,1.6,1.7: msg#00064

video.xine.devel

Subject: Re: Re: [xine-cvs] CVS: xine-vcdnav/doc cd-info.txt,1.6,1.7

On Tue, 2003-08-05 at 14:09, R. Bernstein wrote:
> Bastien Nocera writes:
> > > On Tue, 2003-08-05 at 05:13, R. Bernstein wrote:
> > > <snip>
> > > I'm not sure I understand the problem here. Perhaps you could
> > > elaborate more?
> > >
> > > It is possible to embed a URL inside another and it is done all the time.
> > > Here's an example I just randomly picked:
> > >
> > >
> http://www.yahoo.com/homer/?http://story.news.yahoo.com/news?tmpl=story&u=/ap/20030805/ap_on_re_as/indonesia_blast&cid=516&ncid=716
> >
> > That wouldn't work if we changed the meaning of the POST options, that's
> > the point.
>
> Let me repeat with less ambiguity: I don't I understand the problem
> you are trying to convey. Explain it clearly and in detail.
>
> Someone somewhere may be able to address your concern if you could
> describe the problem you perceive rather than comment on my attempts
> to infer what you mean.
>
> I think this will help in exposition: instead to commenting on
> something I or someone else has written, just start from scratch.
> 1. describe the problem,
> 2. define enough terms for someone to understand what they need to
> understand the problem,
> 3. suggest why your previous simple, straightforward solution doesn't work
> and
> 4. why the current situation in contrast does work (if it does).
>
> In the past I read from you that something's not a "proper URI", which
> I later learn is just not true. Or that some software out there will
> strip @'s in a URI, which by a leap of imagination conceivably could
> be the case if the part in question is part of what RFC 2396 calls
> "userinfo". But if you go through the RFC 2396 grammar for the MRL's
> used here, that's not applicable. And I have yet to learn of a
> particular piece of software, whether it is relevant or not, that
> *does* filter out parts of @'s yet, despite your assertion. #'s as
> was pointed out and as I have tested however *are* filtered by a
> browser and that's what are currently being used.
>
> Again you may have a valid concern, although recently in the past all
> I've been getting is unsupported if not mistaken beliefs. If you or
> someone else can't articulate what the problem is, no one is going to
> be able to figure out if it is valid let alone understand how to
> address it.

Long story short:
How do you know whether "song" is an engine parameter or a POST option
given to the website:
http://play-my-song.foo/baz.cgi?song=foobar

--
/Bastien Nocera
http://hadess.net

#2 0x4205a2cc in printf ("Oh my %s\n", preferred_deity) from
/lib/i686/libc.so.6 printf ("Oh my %s\n", preferred_deity);
Segmentation fault



-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01


<Prev in Thread] Current Thread [Next in Thread>
Google Custom Search

News | FAQ | advertise