How open are you to merging a feature that supports PAC scripts as as in https://en.wikipedia.org/wiki/Web_Proxy_Auto-Discovery_Protocol ?
For clarity, I mean a feature that adds a configuration option
PacUpstream "/path/to/wpad.dat"
and, when specified, tinyproxy uses https://github.com/manugarg/pacparser to find an upstream.
My intended use case is to replace the Twisted-based proxy in https://github.com/tkluck/pac4cli with tinyproxy for better http support. I wrote some initial code here pac4cli@c2b82f3 but it is far from production ready.
Please let me know what you think so I can decide on whether to invest in this approach.
How open are you to merging a feature that supports PAC scripts as as in https://en.wikipedia.org/wiki/Web_Proxy_Auto-Discovery_Protocol ?
For clarity, I mean a feature that adds a configuration option
and, when specified, tinyproxy uses https://github.com/manugarg/pacparser to find an upstream.
My intended use case is to replace the Twisted-based proxy in https://github.com/tkluck/pac4cli with tinyproxy for better http support. I wrote some initial code here pac4cli@c2b82f3 but it is far from production ready.
Please let me know what you think so I can decide on whether to invest in this approach.