httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From r..@engelschall.com (Ralf S. Engelschall)
Subject Re: [PATCH] Unbundling mod_proxy and mod_mime
Date Fri, 13 Mar 1998 08:25:49 GMT

In article <Pine.LNX.3.96dg4.980312115927.3255D-100000@twinlark.arctic.org> you wrote:

> Shouldn't you stuff "proxy:" or something in front of the filename?  Or is
> it already there 'cause r->filename is the proxy subreq?

I had to check this but it is not there, I think. But it should be not
important, I think. Because the sub-request does not run any handler and thus
this should be no problem. Or did I miss something?

> Why isn't there a content_type to begin with?  I mean, you're already in
> the middle of a request for r->filename, and if it works as a
> subrequest... why isn't r->content_type set? 

Yes, this question I asked myself yesterday. I've put an aplog_error call into
the find_ct() function of mod_mime and discovered that it is actually _not_
called for proxy requests while it is (of course) for normal requests. Then
I'm decided that there will be some reason I don't see (because else the
mime_find_ct() wouldn't be needed in the past) and concentrated to just
_replace_ the existing functionality, i.e. finding out the mime type
explicitly.

Does anybody know why the type-checking hook is not called for proxy requests?

                                       Ralf S. Engelschall
                                       rse@engelschall.com
                                       www.engelschall.com

Mime
View raw message