You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have simple firewall that blocks non-browser requests to our websites by checking the user-agent request header. Requests from webpkgserver gets blocked as it uses Go's http client as user-agent.
We're wondering if it's possible for use add custom request header that gets relayed to https://example.com/foo.html so we can use it header to unblock requests from webpkgserver.
we expect to have all requests from webpkgserver to https://example.com/foo.html will have the X-Is-WebPackager: 1 header. But, the custom header is not present which results in the request being blocked by firewall.
Hi!
We have simple firewall that blocks non-browser requests to our websites by checking the user-agent request header. Requests from
webpkgservergets blocked as it uses Go's http client as user-agent.We use Nginx to proxy pass to
webpkgserver. Eg:We're wondering if it's possible for use add custom request header that gets relayed to
https://example.com/foo.htmlso we can use it header to unblock requests fromwebpkgserver.With the config below:
we expect to have all requests from
webpkgservertohttps://example.com/foo.htmlwill have theX-Is-WebPackager: 1header. But, the custom header is not present which results in the request being blocked by firewall.Is it by design?