bleenco / bproxy Goto Github PK

Print to logger time, source-ip, requested hostname, requested url, response time.

• create basic templates for 400, 404, 502 status pages
• load templates from config (optional)
• add how to use in readme

I noticed that watching live job logs on https://ci.bleenco.io only work for some time, let's say job is running 6 minutes but logging is outputed only for 1-2min. When performing a refresh everything works again.
I believe http://docs.libuv.org/en/v1.x/tcp.html#c.uv_tcp_keepalive should be applied somewhere, @martinopresnik will know the best where.

When request is made with multiple chunks (POST request sending data), http parsing crashes on 2nd chunk.

If server behind proxy is already running on SSL it doesn't work while accessing via bproxy configured as SSL.

@martinopresnik please note that this bug is critical and it has very high priority as we currently cannot use HTTP/2 push feature behind on our servers because it requires running on SSL.

Proxy connection never closes.

In case server behind configured proxy stops working websocket connections established via proxy remains open. They should close.

I noticed that sometimes there is something wrong with sent chunks. I don't know for sure what's going on here but might be related if there is websocket connection established also on same time.
I noticed that proxying abstruse and I am appending screenshot:

After some hours of running I got

double free or corruption (!prev)

with program crashing after that. @martinopresnik any idea?

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.

2. 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:

@jkuri please provide a docker to @martinopresnik for setting up this experiments.

Following the issue #54

@martinopresnik let's focus on bombardier or hey to see whether we get similar results to wrk.

Here is the list: https://github.com/denji/awesome-http-benchmark