[Moin-user] Help with script alias in shared hosting
todd.nine at gmail.com
Wed Sep 20 15:18:41 EDT 2006
Thanks for the reply everyone. I tried both solutions but neither worked.
I receive a 500 error on the sourceforge forum posting, and a 400 error on
the suggestions from Matthew. Just an FYI, my host is running Apache 1.3.37.
Here is the error from Matthew's post
"Your browser sent a request that this server could not understand.
Additionally, a 400 Bad Request error was encountered while trying to use an
ErrorDocument to handle the request. "
In my error log I receive the following.
"[Wed Sep 20 13:16:01 2006] [error] [client 188.8.131.52] Invalid URI in
request GET /../gallery/ HTTP/1.0"
Thanks in advance,
On 9/20/06, Matthew Nuzum <newz at bearfruit.org> wrote:
> On 9/19/06, Todd Nine <todd.nine at gmail.com> wrote:
> > I have moin moin working in a shared hosting environment with the
> > following.
> > www/wiki/ (html docs)
> > www/cgi-bin/moin.cgi
> > moin-1_5_4/share/wiki
> > I can get to my site by using "wiki.foo.com/cgi-bin/moin.cgi" and
> > is served correctly.
> > I want to use Alias and ScriptAlias to point the cgi alias as the root
> > and "/wiki/" to the html docs in moin-1_5_4. I only have access to the
> > .htaccess file, can anyone sugest a way to do this?
> According to
> ScriptAlias isn't supported in .htaccess files.
> I logged into my cpanel on bluehost and confirmed that there's no 100%
> satisfactory solution.
> I can think of two ways to make it work nicer... one is to create a
> new handler and rename your cgi file to something more friendly
> looking. Maybe do something like this (haven't tried it yet though)
> in Cpanel go to Apache Hanlders under the "Web Server Config" section
> extension = .wiki
> handler = cgi-script
> Rename moin.cgi to moin.wiki and put it in your root folder. Then you
> may be able to access your wiki as http://foo.com/moin.wiki/FrontPage
> Get creative and you could boost your search engine ranking:
> foo.com/XYZ.wiki/FrontPage (where XYZ is something you want to
> optimize for)
> Second option is to use rewrite rules, which I believe *are* allowed.
> Here's something I use that you can experiment with: (I've modified to
> make it hopefully more useful to you)
> RewriteEngine on
> RewriteRule !(htdocs|images|robots.txt|favicon.ico|cgi-bin)
> RewriteOptions inherit
> Matthew Nuzum
> newz2000 on freenode
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Moin-user