Browse Source

Update notes of 'patch_apache_break_http_code_standard.patch'

master
Pekka Helenius 6 years ago
committed by GitHub
parent
commit
d20b3156b2
No known key found for this signature in database GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 9 additions and 5 deletions
  1. +9
    -5
      patches/patch_apache_break_http_code_standard.patch

+ 9
- 5
patches/patch_apache_break_http_code_standard.patch View File

@ -1,22 +1,26 @@
Author: Pekka Helenius (~Fincer), 2018 Author: Pekka Helenius (~Fincer), 2018
This is an experimental patch, just introducing the principle of manipulating HTTP header response codes returned by Apache HTTP server to a client. The patch is mainly for personal use, nothing else. If you see it worth it, feel free to use it. And absolutely, feel free to modify it! If you see it just awful, ignore it. Thanks.
This patch may break things badly, just be aware and proceed with care! Thanks.
This is an experimental patch, just introducing the principle of manipulating HTTP header response codes returned by
Apache HTTP server to a client. The patch is mainly for personal use, nothing else. If you see it worth it, feel free
to use it.
And absolutely, feel free to modify it! If you see it just awful, ignore it. Thanks.
The patch breaks HTTP standard by altering HTTP header response codes generated by Apache HTTP server. Generated codes are: The patch breaks HTTP standard by altering HTTP header response codes generated by Apache HTTP server. Generated codes are:
If client request generates HTTP response code 401, the server returns error code 401. If client request generates HTTP response code 401, the server returns error code 401.
If client request generates HTTP response code 401->, the server returns error code 400. If client request generates HTTP response code 401->, the server returns error code 400.
If client request generates HTTP response code 500->, the server returns error code 400 instead. If client request generates HTTP response code 500->, the server returns error code 400 instead.
Any other codes (100-308) will be returned normally, including 200 OK message. Any other codes (100-308) will be returned normally, including 200 OK message.
Remember to comment any unsupported ErrorDocument fields from your VirtualHost configurations before starting the server with this patch applied.
Remember to comment any unsupported ErrorDocument directive fields from your VirtualHost configurations
before starting the server with this patch applied.
All Apache HTTP response codes are listed in 'modules/http/http_protocol.c' file. All Apache HTTP response codes are listed in 'modules/http/http_protocol.c' file.
This patch may break things badly, just be aware and proceed with care! Thanks.


Loading…
Cancel
Save