Yes, my load-balancer is responsible for caching as well and correctly set the header X-Forwarded-For.
Actually, I really need the mod_remoteip because I want the real IP in the access_log . Laurent On Sep 10, 1:10 pm, pghoratiu <pghora...@gmail.com> wrote: > Is the load balancer responsible for caching as well? > Checkhttp://en.wikipedia.org/wiki/X-Forwarded-Forand retrieve the > client IP address from that HTTP header. > You don't need anything extra on the Apache side. > > gabriel > > On Sep 10, 12:52 pm, Laurent Vaills <laurent.vai...@gmail.com> wrote: > > > Hi, > > > I am developping a website using symfony 1.4 on CentOS 5 (httpd 2.2.3, > > php 5.2.10). > > I have compiled the mod_remoteip on the httpd 2.2 (because this module > > is only available for httpd 2.3). > > But the IP that is reported by Apache is the one of our load-balancer. > > > After some tests, I've found that the problem comes from the > > RewriteRule. Is it possible to moMy problem is that the mod_remoteip > > does not work with rewrite rule defined by symfony. > > > Does anyone succeeded to have symfony and mod_remoteip working > > together ? > > > Regards, > > Laurent -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to symfony-users@googlegroups.com To unsubscribe from this group, send email to symfony-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en
