On 21.04.2011, at 15:49, David Zülke wrote: > You can map any $_SERVER field too, for instance in case you're running > behind a load balancer (this one is for EC2 LBs):
Actually, that wasn't the whole truth. You can only map the ones that AgaviWebRequest uses: HTTPS, REQUEST_METHOD, SERVER_NAME, SERVER_PORT, SERVER_PROTOCOL and SERVER_SOFTWARE (see http://trac.agavi.org/ticket/1029). The cool thing is though that you can also give static values if you want. Let's assume your site is HTTPS only in production, and your load balancer terminates the SSL connection, but it sucks and can't forward the port (443) and transport (HTTPS) info to the backend servers which would then think it was plain HTTP and port 80: <ae:configuration environment="production.*" context="web"> <request class="AgaviWebRequest"> <ae:parameter name="sources"> <ae:parameter name="SERVER_PORT">443</ae:parameter> <ae:parameter name="HTTPS">on</ae:parameter> </ae:parameter> </request> </ae:configuration>
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ users mailing list [email protected] http://lists.agavi.org/mailman/listinfo/users
