New Message: Re: Serving a single file

[Larry Curtin]

Mod_rewrite? 

Just do a rewrite directing the default apache server request back to
frontier.

-----Original Message-----
From: manila-users-bounces at userland.com
[mailto:manila-users-bounces at userland.com] On Behalf Of
webmaster at userland.com
Sent: Thursday, February 02, 2006 2:33 PM
To: manila-users at userland.com
Subject: New Message: Re: Serving a single file

A new message was posted:

Address: http://manila.userland.com/discuss/msgReader$1604

By: Matt Deatherage (frontier at gcsf.com)

/I think that would be
http://www.example.com:8080/mySite/files/myFile.xml. If you're using
Apache with port rewriting, it should translate the :8080 URL to
http://www.example.com/mySite/files/myFile.xml./

Sam: That's a bit of a thing, isn't it? If 8080 is the port Frontier is
really running on, then yes, Apache port rewriting changes the 8080 to
80 (or "nothing") so the URL comes out with no port number.

But if I actually want Apache to serve the file, I can't send the URL
through Frontier, right? So I have Apache running "naked" on port 81,
and all of my gems URLs start "www.example.com:81", which poses part of
my problem. I had hoped to have Frontier serve this one file instead of
Apache because I can't figure out how to do it the other way.

I installed Filer, but apparently I missed something - if I have it
disable gems, then all of the already-uploaded gems don't appear in
Filer, and that's no good.

--Matt

This is a Manila site... http://manila.userland.com/.