v0.7.0

Added

• The following new properties can be used to specify the maximum allowed size
  of the individual parts of an HTTP request or response header.
  • http.header.request.request_line_size_limit
  • http.header.response.status_line_size_limit
  • http.header.request.fields_limit
  • http.header.response.fields_limit
  • http.header.request.field_size_limit
  • http.header.response.field_size_limit

Changed

• The properties http.header.request.max_size and http.header.response.max_size
  have been removed. Using the newly introduced properties, the allowed size of
  an HTTP header can be specified more precisely.

v0.6.1

Changed

• When the server sends the HTTP status code 101 (Switching Protocols),
  the status code 502 (Bad Gateway) is instead sent to the client.
• The proxy closes connections immediately after the HTTP response to a
  HTTP request has been submitted.

Fixed

• All HTTP header fields, which are listed in the HTTP header field Connection,
  are removed from an HTTP message. So far only the HTTP header field Upgrade
  has been removed.

v0.6.0

Changed

• All HTTP requests using a different HTTP protocol version than 1.1 are
  rejected with the HTTP status code 505 (HTTP Version Not Supported).
• All HTTP responses using a different HTTP protocol version than 1.1 are
  rejected with the HTTP status code 502 (Bad Gateway).
• The HTTP header fields Connection and Upgrade are removed from all HTTP
  messages.
• When the server sends the HTTP status code 426 (Upgrade Required), the status
  code 502 (Bad Gateway) is instead sent to the client.

v0.5.0

Added

• All HTTP requests and responses are standardized before they are forwarded to
  the server and clients. The names of header fields are converted completely
  into lowercase letters.
• HTTP requests with syntactically incorrect request lines or header fields are
  rejected with the HTTP status code 400 (Bad Request). Such requests are not
  forwarded to the target server.
• HTTP responses with syntactically incorrect status lines or header fields are
  rejected with the HTTP status code 502 (Bad Gateway). Such responses are not
  forwarded to clients.
• The proxy supports chunked transfer coding if chunked is the last coding in a
  sequence of transfer codings. So far, chunked was only supported, if it was
  the only transfer coding.

v0.4.2

Fixed

• Name of the monitor thread corrected.

v0.4.1

Fixed

• If an error occurs while transferring the server's HTTP response to the client,
  GALOP is trying to send a suitable HTTP status code to the client. If parts of
  the HTTP response have already been sent to the client, so far they are mixed
  with this HTTP status code. Instead, GALOP now close the connection so that no
  invalid response is sent to the client.

v0.4.0

Added

• If the proxy can not establish a TCP connection with the server within a
  configured time, the proxy sends the HTTP status code 504 (Gateway Time-out)
  to the client.
• If a connection to the server can not be established, the proxy sends the
  HTTP status code 503 (Service Unavailable) to the client.
• If the client does not send a full HTTP request header to the server within
  a configured time, the proxy sends the HTTP status code 408 (Request Time-out)
  to the client.
• If the server does not send a full HTTP response header to the client within
  a configured time, the proxy sends the HTTP status code 504 (Gateway Time-out)
  to the client.
• The requested maximum number of pending connections on the proxy socket can be
  configured.
• The local address the proxy socket will bind to can be configured.

Changed

• The maximum allowed size of an HTTP header can be configured separately for
  requests and responses.
• The property security.max_http_header_size has been replaced by the new
  properties http.header.request.max_size and http.header.response.max_size.
• The following configuration properties have been renamed:
  • proxy_port to proxy.port
  • target_address to target.address
  • target_port to target.port
  • connection_handlers.termination_timeout to http.connection.termination_timeout
  • connection_handlers.log_interval to http.connection.log_interval

v0.3.1

Changed

• Apache Log4j updated to version 2.8.2.

v0.3.0

Added

• Support for chunked transfer encoding.
• When GALOP is started, the following events are additional logged:
  • Loading of the configuration file and the result.
  • The initialization of the server socket.

v0.2.0

Added

• If the client sends an invalid HTTP request or the server sends an invalid HTTP response, the proxy now sends an error message to the client.
• If an error occurred while processing the server response, the proxy sends the HTTP status code 502 Bad Gateway to the client and logs the error.