Re: fancy redirects / 404 passthrough

Hmm... that behavior doesn't really seem clear from
the docs, I would think that having a built in 404
handler, Tux would not be "unsure" about how to
process the request.  I will look into this and post
the results.

Thanks!

--- Ingo Molnar <[email protected]> wrote:
> 
> On Wed, 29 Oct 2003, human bn wrote:
> 
> > >From the docs:
> > -----
> > 404_page: If Red Hat Content Accelerator does not
> > manage to look up a requested page then it first
> tries
> > to look up the document specified in 404_page. If
> the
> > 404 page can not be found, the canned 404 message
> is
> > sent. The file is relative to the document root.  
> > -----
> > OK, how do you disable 404 handling completely? 
> Just
> > make the request pass through?
> 
> have you considered this portion of the
> documentation:
> 
>      * Whenever  Red  Hat  Content Accelerator is
> unsure how to process a
>        request  or  receives  a request it is unable
> to handle, it always
>        redirects  the  request  to  the  user-space 
> web server daemon to
>        handle   it  in  an  RFC-compliant  manner. 
> An  example  of  this
>        user-space web server daemon is Apache.
> 
> a 404 is only sent if the secondary server does not
> listen on the
> secondary port. (ie. if Apache is not running or is
> not set up properly to
> be the secondary server to Tux.)
> 
> 	Ingo
> 
> 
> _______________________________________________
> tux-list mailing list
> [email protected]
> https://www.redhat.com/mailman/listinfo/tux-list


__________________________________
Do you Yahoo!?
Exclusive Video Premiere - Britney Spears
http://launch.yahoo.com/promos/britneyspears/