M031097
asked on
Adding custom request header
Hello
Is there any way of adding a request header on apache 1.3.26 and if so, how?
I saw that Apache2 has this feature included:
RequestHeader set nameofheader
but for version 1.3.26 you can only add response headers
(AFAIK)
So, how do I add a custom request header?
Regards
M
Is there any way of adding a request header on apache 1.3.26 and if so, how?
I saw that Apache2 has this feature included:
RequestHeader set nameofheader
but for version 1.3.26 you can only add response headers
(AFAIK)
So, how do I add a custom request header?
Regards
M
pjedmond
I don't think so, but as I've never tried it on this version I can not be 100% certain:( As the software is free, is there any reason why you can't just upgrade?
M,
as confirmed by Apache website (http://httpd.apache.org/docs-2.0/mod/mod_headers.html), the module is available only in Apache2.
as confirmed by Apache website (http://httpd.apache.org/docs-2.0/mod/mod_headers.html), the module is available only in Apache2.
ASKER
I cannot upgrade unfortunatly.
Why do you need the request header feature with Apache 1.3.X ? What do you want to do ?
In fact it's not available prior to 2.x for security reasons.
ASKER
Ok...what I want to do is have the apache 1.3.26 (used for authentication) proxy to squid. Squid acts as an accelerator for OWA/Exchange2k.
Everything works fine except that the OWA generates the client pages with http://myserver.etc.com
If I add the request header:
front-end-https: on
the OWA will generate the pages with https://myserver.etc.com
so if my initial connection is over SSL, the OWA generates pages that gets the client to connect over http
That is my real problem, and I cannot upgrade to 2.x (which I would really like to do since basically all my problem would go away)
regards
M
M,
Interesting stuff yu're trying to do ! Tell me if I'm wrong but yu just want to relay all your clients that have accessed to OWA to an SSL connection ?
By the way, do you really need Squid as accelerator for OWA ?
Interesting stuff yu're trying to do ! Tell me if I'm wrong but yu just want to relay all your clients that have accessed to OWA to an SSL connection ?
By the way, do you really need Squid as accelerator for OWA ?
even apache 1.3 could be operated as accelerator. and if you had SSL configured , voila you had SSL connection to your apache that proxied you internal OWA
A combination of VirtualHost and mod_proxy would do the job.
cheers.
A combination of VirtualHost and mod_proxy would do the job.
cheers.
ASKER
well maybe you are right samri, but it isn't what I want to do.
The above is the main, but only part of the solution....
/M
The above is the main, but only part of the solution....
/M
M,
since the limitation lies on the software itself, personally the option that is left (IMHO) would be either to upgrade, hack apache itself to include the feature, or run two version of apache parallel - your existing 1.3 for your existing website, and Apache2, just for the OWA stuff.
This may sound a bit unrealistic, but should work.
since the limitation lies on the software itself, personally the option that is left (IMHO) would be either to upgrade, hack apache itself to include the feature, or run two version of apache parallel - your existing 1.3 for your existing website, and Apache2, just for the OWA stuff.
This may sound a bit unrealistic, but should work.
ASKER
No the problem is that I am dependant on the 1.3 for the authentication part...but regardless I cannot use two processes since the fire wall blocks all but 80/443.
No matter, I have found the solution elsewhere:
http://www.mail-archive.com/modssl-users@modssl.org/msg15460.html
of course, I need to comile a new module which "sucks" in a way, but...it'll have to do.
/M
No matter, I have found the solution elsewhere:
http://www.mail-archive.com/modssl-users@modssl.org/msg15460.html
of course, I need to comile a new module which "sucks" in a way, but...it'll have to do.
/M
M,
That was a great solution that you manage to dig off the web. And thanks for sharing it with us.
The fact that you need to build the module is good -- at least there is still an option.
Anyway, since the problem is practically solved, you could request a refund in Community Support.
cheers.
That was a great solution that you manage to dig off the web. And thanks for sharing it with us.
The fact that you need to build the module is good -- at least there is still an option.
Anyway, since the problem is practically solved, you could request a refund in Community Support.
cheers.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.