* Thomas Leonard <tal00r@...> [30/05/2003 0652EDT]:
> On Thu, May 29, 2003 at 11:34:02AM -0400, Keith R. John Warno wrote:
> > I just made the move from ROX-Filer 1.3.8 to 1.3.10 on a system at work,
> > rolling my own rpm package as usual and installing system-wide.
> >
> > Upon starting 1.3.10 I get a nice message saying that ~/.mime has moved
> > to ~/.local/share/mime/, etc etc etc. (src/type.c:1234). When did this
> > happen and why?
>
> The MIME spec changed to use the new Base Directory Specification
> (http://www.freedesktop.org/standards/basedir/draft/basedir-spec/
> basedir-spec.html).
I'll have to read the spec to see exactly why it is is necessary to have
the mime dir three levels deep within a user's home dir. :-/ I've
always had the notion that anything within a user's home dir is
*implicitly* local; if to have this ~/.local/ dir is for descriptive
purposes only, it is entirely redundant and simply unnecessary. But
like I said, I'll have to read the spec.
> > On another note, I'm finding that when downloading rox-x.y.z.tgz from
> > the SF mirrors, the file is being gratuitously gunzipped on the fly.
> > This is an HTTP server config thing; someone at SF should be enlightened
> > to it...
>
> Doesn't affect me...
Will depend on browser too. From apache's httpd.conf:
#
# AddEncoding allows you to have certain browsers (Mosaic/X 2.1+) uncompress
# information on the fly. Note: Not all browsers support this.
# Despite the name similarity, the following Add* directives have nothing
# to do with the FancyIndexing customization directives above.
#
#AddEncoding x-compress Z
#AddEncoding x-gzip gz tgz
These two lines are uncommented *by default*.
Of course this means most (all?) modern browsers. But if the
AddEncoding lines aren't there, the decompression won't happen at all
regardless of browser (or so I beleive). I use mozilla 1.4b; there
could be something going on I am just not aware of. :-) I also found
it depends on which mirror I d/l from (further suggesting an httpd
config issue).
These will be decompressed on the fly:
http://aleron.dl.sourceforge.net/sourceforge/rox/rox-1.3.10.tgz
(Reston, VA)
http://unc.dl.sourceforge.net/sourceforge/rox/rox-1.3.10.tgz
(Chapel Hill, NC)
http://umn.dl.sourceforge.net/sourceforge/rox/rox-1.3.10.tgz
(Minneapolis, MN)
http://heanet.dl.sourceforge.net/sourceforge/rox/rox-1.3.10.tgz
(Dublin, Ireland)
These will not:
http://easynews.dl.sourceforge.net/sourceforge/rox/rox-1.3.10.tgz
(Phoeniz, AZ)
http://switch.dl.sourceforge.net/sourceforge/rox/rox-1.3.10.tgz
(Zurich, Switzerland)
http://cesnet.dl.sourceforge.net/sourceforge/rox/rox-1.3.10.tgz
(Prague, Czech Republic)
Sure enough, a little further investigation with netcat shows the
following HTTP headers for a mirror that induces the decompression:
kw@...]:~$ \
> echo -en 'GET /sourceforge/rox/rox-1.3.10.tgz HTTP/1.0\n\n' | \
> netcat aleron.dl.sourceforge.net 80 | sed -e '/^[[:space:]]*$/q'
HTTP/1.1 200 OK
Date: Fri, 30 May 2003 13:57:46 GMT
Server: Apache/2.0.45 (Unix)
Last-Modified: Thu, 29 May 2003 11:14:28 GMT
ETag: "207c07f-176a1c-a9e30d00"
Accept-Ranges: bytes
Content-Length: 1534492
Connection: close
Content-Type: application/x-tar-gz
Content-Encoding: x-gzip
... and the following for a server that does NOT induce the
decompression:
kw@...]:~$ \
> echo -en 'GET /sourceforge/rox/rox-1.3.10.tgz HTTP/1.0\n\n' | \
> netcat cesnet.dl.sourceforge.net 80 | sed -e '/^[[:space:]]*$/q'
HTTP/1.1 200 OK
Date: Fri, 30 May 2003 13:59:20 GMT
Server: Apache/2.0.46 (Red Hat Linux)
Last-Modified: Thu, 29 May 2003 11:14:28 GMT
ETag: "9983ef-176a1c-a9e30d00"
Accept-Ranges: bytes
Content-Length: 1534492
Connection: close
Content-Type: application/x-tar-gz
I rest my case.
--
Keith R. John Warno [k r j w at optonline dot net]
"I know the human being and fish can coexist peacefully."
-- George "Dubuhyuh" Bush, Saginaw, Mich, Sept 29, 2000
|