Bug 33203 - mod_proxy_ajp should use ssl_is_https hook
Summary: mod_proxy_ajp should use ssl_is_https hook
Status: RESOLVED FIXED
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: mod_proxy (show other bugs)
Version: 2.1-HEAD
Hardware: PC Linux
: P2 normal (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
URL:
Keywords: PatchAvailable
Depends on:
Blocks:
 
Reported: 2005-01-21 21:49 UTC by Brad Boyer
Modified: 2005-04-09 10:21 UTC (History)
0 users


Attachments
Patch to use mod_ssl hooks to detect is_ssl (2.54 KB, patch)
2005-01-21 21:51 UTC, Brad Boyer 		Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Brad Boyer 2005-01-21 21:49:23 UTC 
The AJP code doesn't set the is_ssl field in the outbound data. This causes
tomcat to think that every connection is really coming in on http. Without this
data, any redirects generated by tomcat that should go back to an https URL on
apache get sent to http instead. I'm sure other stuff goes wrong, too.
Comment 1 Brad Boyer 2005-01-21 21:51:33 UTC 
Created attachment 14065 [details]
Patch to use mod_ssl hooks to detect is_ssl

This patch adds in functions to load and wrap the ssl_is_https function similar
to the other ssl optional hooks and sets is_ssl in the ajp_header code
according to the return value from the ssl code.
Comment 2 Mladen Turk 2005-04-09 18:21:34 UTC 
Commited, thanks.
I only rename the function from is_ssl to is_https.