On Wed, Jul 27, 2011 at 9:35 AM, Stefan Fritsch <s...@sfritsch.de> wrote: > On Wednesday 27 July 2011, Petr Hracek wrote: >> Dear users, >> >> I have one simple question. >> Is there any possibility how to "call" module from the another >> module? >> >> Let's say that my module is used for checking whether user is >> logged, session is expired, etc. >> When all those tests are satisfied then URL which was checked by my >> module is redirect to another module e.g proxy? >> >> https://<IP_address>/APPL1 should be authenticated by my own >> proprietary module and when this is successed then it is redirect >> to proxy defined in /etc/apache/conf/my_conf.conf file >> >> <VirtualHost _default_:443> >> SSLEngine on >> SSLProxyEngine on >> ProxyRequests Off >> TraceEnable Off >> >> <Proxy *> >> AuthType SEC_CHECK >> require valid-user >> satisfy Any >> </Proxy> >> </VirtualHost> >> >> ProxyPass /APPL1 http://192.0.2.20:8080/APPLONE >> ProxyPassReverse /APPL1 http://192.0.2.20:8080/APPLONE >> >> AuthType in my module SEC_CHECK is defined so: >> #defined SECURITY_AUTH_CHECK "SEC_CHECK" >> r->ap_auth_type = SECURITY_AUTH_CHECK >> Is this "behaviour" possible? > > mod_proxy should handle the request with you having to do anything in > your module. Have you tried replacing your auth module with basic auth > and checked if that works? If no, there is likely some other problem > in your config. >
If it wasn't already intended to be reverse proxied, or successful auth in your mod changes where it's destined for, see how mod_rewrite implements the [P] flag to pass along a request to mod_proxy. -- Eric Covener cove...@gmail.com
