Skip to content
This repository was archived by the owner on Feb 13, 2026. It is now read-only.
This repository was archived by the owner on Feb 13, 2026. It is now read-only.

Option for webpkgserver to relay custom headers  #114

Description

@sandyandi

Hi!

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 use Nginx to proxy pass to webpkgserver. Eg:

proxy_pass http://127.0.0.1:8080/priv/doc/https://example.com/foo.html;

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.

With the config below:

proxy_pass    http://127.0.0.1:8080/priv/doc/https://example.com/foo.html;
proxy_set_header    X-Is-WebPackager    1

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.

Is it by design?

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions