Chain proxy methods (HTTP/HTTPS then FastCGI w/ ROLE=filter)
I'm working on a project involving setting up a web server as a proxy such that:
http://host/proxy/http//www.google.com/ --> http://www.google.com
http://host/proxy/https//www.gmail.com/ --> https://www.gmail.com
That seems to be partly ok (Not sure if the http,https part works..)
One part of this involves throwing the data through a FastCGI filter to perform modifications such as fixing links/etc as well as other custom items depending on page. From my understanding you can't put a FastCGI filter in, so my current implementation would be to fetch the data in my FastCGI handler... but that's suboptimal, I think.
Not quite sure how configuration would look either....
-- Thomas Harning Jr. <harning
Updated by gstrauss about 3 years ago
- Status changed from New to Wontfix
so my current implementation would be to fetch the data in my FastCGI handler... but that's suboptimal, I think.
Why not? Sounds reasonable.
Similar to what was noted in #1187, lighttpd is (primarily) an origin server, and does not currently provide features of an intermediate caching proxy. Additionally, FastCGI filter role does not appear to be implemented in most/any popular/still-relevant webservers, suggesting that there are viable alternatives, such as using a web server framework for HTTP proxying in your favorite scripting language and performing transformations on the content as desired.
Sorry, implementing FastCGI 'filter' role is not a priority in lighttpd at this time.
Also available in: Atom