Skip to content

Figure out the correct way to configure trust proxy and HTTP_FORWARDED_COUNT #979

Open
@make-github-pseudonymous-again

Description

Maybe this has to be configured for Meteor's router, or maybe this is incorrectly applied twice.

This currently does not work in api/healthcheck and api/ics. The consequence is that all requests fall in the same rate-limiting bucket, which is a UX concern as soon as we have more than one user.

See:

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingdeployThis issue is about deploymentsecurityThis issue is about the overall security of the application

    Type

    No type

    Projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions