You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mbox-dev@httpd.apache.org by "William A. Rowe, Jr." <wr...@rowe-clan.net> on 2001/09/20 17:33:33 UTC
MBOX url format
To a list where it's quite relevant ;)
----- Original Message -----
From: "Alex Stewart" <al...@foogod.com>
To: <de...@httpd.apache.org>
Sent: Thursday, September 20, 2001 2:53 AM
Subject: Re: cvs commit: httpd-2.0/server/mpm/worker worker.c
> On a largely unrelated note, but something I found a little ironic given
> the nature of this list:
>
> Aaron Bannert wrote:
>
> > http://www.apachelabs.org/apache-mbox/199902.mbox/<36...@raleigh.ibm.com>
>
>
> Please note that the above is not a valid URL. Specifically, the "<"
> and ">" characters are technically not allowed in URLs and must be
> escaped. (I bring this up partly because in Mozilla, this message came
> up with two links, a http: link to 199902.mbox, and a mailto: link to
> 36D1B5C1.87A3EC11@raleigh.ibm.com, so I had to do some cutting and
> pasting to actually see the right document)
>
> Whoever does the software behind apache-mbox (I take it this is
> mod_mbox?) might want to take note that it's spitting out invalid URLs..
>
> -alex
>
>
>
>
>
>
Re: MBOX url format
Posted by Aaron Bannert <aa...@clove.org>.
On Thu, Sep 20, 2001 at 09:45:41AM -0700, Justin Erenkrantz wrote:
> On Thu, Sep 20, 2001 at 08:43:46AM -0700, Aaron Bannert wrote:
> > Just for the record, this URL was produced from the Location: bar from
> > my browser. The URLs generated from mod_mbox appear to be properly escaped
> > for the < and > cases. For some reason my Netscape chose to unescape it.
> > Could be a Netscape bug, or could be something we're doing that makes
> > Netscape want to unescape it for display in the Location: bar.
> >
> > I think I mentioned this before, but we may want to just parse out and
> > remove the < and >'s from the MessageIDs, assuming all MessageIDs have
> > them. (I'm just suggesting, not volunteering :)
>
> % mozilla --version
> Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.4) Gecko/20010914, build 2001091501
>
> Pasted from Mozilla's Location bar:
>
> http://www.apachelabs.org/apache-mbox/200109.mbox/%3c9CF6FAED416EA043A968ED643E1371950C4D00@prima-exc01.cidadei.com.br%3e
>
> % netscape --version
> Netscape 4.78/U.S., 25-Jun-01; (c) 1995-2000 Netscape Communications Corp.
>
> Pasted from Netscape's Location bar:
>
> http://www.apachelabs.org/apache-mbox/200109.mbox/%3c9CF6FAED416EA043A968ED643E1371950C4D00@prima-exc01.cidadei.com.br%3e
>
> If you would like to go through and normalize the Message-IDs by
> removing the <>s, you would have to be my guest. =)
>
> I'll warn you that it makes the parsing harder to perform if you
> make it different than what the actual Message-ID MIME header
> value is. -- justin
Relax, nobody's saying mod_mbox is broken.
Like I said, it's probably my Netscape (v4.75).
-aaron
Re: MBOX url format
Posted by Justin Erenkrantz <je...@ebuilt.com>.
On Thu, Sep 20, 2001 at 08:43:46AM -0700, Aaron Bannert wrote:
> Just for the record, this URL was produced from the Location: bar from
> my browser. The URLs generated from mod_mbox appear to be properly escaped
> for the < and > cases. For some reason my Netscape chose to unescape it.
> Could be a Netscape bug, or could be something we're doing that makes
> Netscape want to unescape it for display in the Location: bar.
>
> I think I mentioned this before, but we may want to just parse out and
> remove the < and >'s from the MessageIDs, assuming all MessageIDs have
> them. (I'm just suggesting, not volunteering :)
% mozilla --version
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.4) Gecko/20010914, build 2001091501
Pasted from Mozilla's Location bar:
http://www.apachelabs.org/apache-mbox/200109.mbox/%3c9CF6FAED416EA043A968ED643E1371950C4D00@prima-exc01.cidadei.com.br%3e
% netscape --version
Netscape 4.78/U.S., 25-Jun-01; (c) 1995-2000 Netscape Communications Corp.
Pasted from Netscape's Location bar:
http://www.apachelabs.org/apache-mbox/200109.mbox/%3c9CF6FAED416EA043A968ED643E1371950C4D00@prima-exc01.cidadei.com.br%3e
If you would like to go through and normalize the Message-IDs by
removing the <>s, you would have to be my guest. =)
I'll warn you that it makes the parsing harder to perform if you
make it different than what the actual Message-ID MIME header
value is. -- justin
Re: MBOX url format
Posted by Aaron Bannert <aa...@clove.org>.
Just for the record, this URL was produced from the Location: bar from
my browser. The URLs generated from mod_mbox appear to be properly escaped
for the < and > cases. For some reason my Netscape chose to unescape it.
Could be a Netscape bug, or could be something we're doing that makes
Netscape want to unescape it for display in the Location: bar.
I think I mentioned this before, but we may want to just parse out and
remove the < and >'s from the MessageIDs, assuming all MessageIDs have
them. (I'm just suggesting, not volunteering :)
-aaron
On Thu, Sep 20, 2001 at 10:33:33AM -0500, William A. Rowe, Jr. wrote:
> To a list where it's quite relevant ;)
>
> ----- Original Message -----
> From: "Alex Stewart" <al...@foogod.com>
> To: <de...@httpd.apache.org>
> Sent: Thursday, September 20, 2001 2:53 AM
> Subject: Re: cvs commit: httpd-2.0/server/mpm/worker worker.c
>
>
> > On a largely unrelated note, but something I found a little ironic given
> > the nature of this list:
> >
> > Aaron Bannert wrote:
> >
> > > http://www.apachelabs.org/apache-mbox/199902.mbox/<36...@raleigh.ibm.com>
> >
> >
> > Please note that the above is not a valid URL. Specifically, the "<"
> > and ">" characters are technically not allowed in URLs and must be
> > escaped. (I bring this up partly because in Mozilla, this message came
> > up with two links, a http: link to 199902.mbox, and a mailto: link to
> > 36D1B5C1.87A3EC11@raleigh.ibm.com, so I had to do some cutting and
> > pasting to actually see the right document)
> >
> > Whoever does the software behind apache-mbox (I take it this is
> > mod_mbox?) might want to take note that it's spitting out invalid URLs..
> >
> > -alex
> >
> >
> >
> >
> >
> >