#1281: Forcing the url scheme to https is not possible
-----------------------------------------+----------------------------------
Reporter: sven.kretschm...@… | Owner: david
Type: defect | Status: new
Priority: normal | Milestone: 1.0.4
Component: request | Version: 1.0.3
Severity: normal | Keywords:
Has_patch: 0 |
-----------------------------------------+----------------------------------
Comment(by david):
Just to understand this correctly... you have Squid proxying HTTPS
requests to web servers via HTTP, and thus you configure a static value
for {{{$_SERVER["HTTPS"]}}}, and the expected "on" gets converted to a
boolean by the config handler, right?
I guess we can fix that. I need to investigate what the possible values
for {{{$_SERVER["HTTPS"]}}} are on different web servers (maybe some web
server sets it to "off" if it's a regular HTTP request...). In the
meantime, is there a way to tell squid to set a certain header that you
could use instead? Then you could do, for instance
{{{
#!xml
<request>
<ae:parameter name="sources">
<ae:parameter name="HTTPS">HTTP_X_FORWARDED_HTTPS</ae:parameter>
</ae:parameter>
</request>
}}}
--
Ticket URL: <http://trac.agavi.org/ticket/1281#comment:1>
Agavi <http://www.agavi.org/>
An MVC Framework for PHP5
_______________________________________________
Agavi Tickets Mailing List
[email protected]
http://lists.agavi.org/mailman/listinfo/tickets
