What is the overhead when redirect through mod_proxy
- by ivoba
I have an API that used to run on Apache but now is served via lighttpd. I can easily switch the API URL in the app to the lighty port like api.net:81. I wonder if I should use mod_proxy instead to have cleaner urls. There is no redirect for legacy urls necessary. What would be the overhead for the Apache in between compared to the direct call?
Would mod_proxy and Apache steal the benefit of lightys lightweightness?