Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[feat]: additional headers #23

Closed
jkuri opened this issue May 4, 2018 · 0 comments · Fixed by #33
Closed

[feat]: additional headers #23

jkuri opened this issue May 4, 2018 · 0 comments · Fixed by #33
Assignees

Comments

@jkuri
Copy link
Contributor

jkuri commented May 4, 2018

  1. Request

Each proxy should send additional headers with initial request so the server behind proxy knows information about the client.
Check https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers the Proxy section;

  • X-Forwarded-For
    Identifies the originating IP addresses of a client connecting to a web server through an HTTP proxy or a load balancer.
  • X-Forwarded-Host
    Identifies the original host requested that a client used to connect to your proxy or load balancer.
  • X-Forwarded-Proto
    identifies the protocol (HTTP or HTTPS) that a client used to connect to your proxy or load balancer.
  1. Response

Add our own header in response so if someone checks it knows it was proxied by our reverse proxy,
just like everyone else do.

header name is server, add server: bproxy [VERSION], example for nginx:

screen shot 2018-05-04 at 16 42 48

martinopresnik added a commit to martinopresnik/bproxy that referenced this issue Jun 1, 2018
martinopresnik added a commit to martinopresnik/bproxy that referenced this issue Jun 1, 2018
martinopresnik added a commit to martinopresnik/bproxy that referenced this issue Jun 1, 2018
@jkuri jkuri closed this as completed in #33 Jun 1, 2018
jkuri pushed a commit that referenced this issue Jun 1, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants