diff --git a/requests/errors/default/400.http b/requests/errors/default/400.http new file mode 100644 index 0000000..2a1c376 --- /dev/null +++ b/requests/errors/default/400.http @@ -0,0 +1,72 @@ +HTTP/1.1 400 Bad Request +Cache-Control: no-cache +Connection: close +Content-Type: text/html + + + + + + + 400 Bad Request + + + +
+

400 Bad Request

+

Oops! Something went wrong with your request.

+
+
+

+ Why did the server go broke? Because it couldn't process any requests! +

+
+ + + diff --git a/requests/errors/default/401.http b/requests/errors/default/401.http new file mode 100644 index 0000000..13a4ee8 --- /dev/null +++ b/requests/errors/default/401.http @@ -0,0 +1,73 @@ +HTTP/1.1 401 Unauthorized +Cache-Control: no-cache +Connection: close +Content-Type: text/html + + + + + + + 401 Unauthorized + + + +
+

401 Unauthorized

+

Oops! Access is denied. You are not authorized to view this page.

+
+
+

+ Why did the hacker break up with his computer? He found out it was + "encrypting" with someone else behind his back! +

+
+ + + diff --git a/requests/errors/default/402.http b/requests/errors/default/402.http new file mode 100644 index 0000000..b847783 --- /dev/null +++ b/requests/errors/default/402.http @@ -0,0 +1,73 @@ +HTTP/1.1 402 Payment Required +Cache-Control: no-cache +Connection: close +Content-Type: text/html + + + + + + + 402 Payment Required + + + +
+

402 Payment Required

+

Oops! You need to pay to access this resource.

+
+
+

+ Why did the web developer always carry a credit card? To handle all + those "payment required" errors! +

+
+ + + diff --git a/requests/errors/default/403.http b/requests/errors/default/403.http new file mode 100644 index 0000000..8454783 --- /dev/null +++ b/requests/errors/default/403.http @@ -0,0 +1,73 @@ +HTTP/1.1 403 Forbidden +Cache-Control: no-cache +Connection: close +Content-Type: text/html + + + + + + + 403 Forbidden + + + +
+

403 Forbidden

+

Oops! Access to this resource is forbidden.

+
+
+

+ Why did the computer get grounded? It kept accessing "forbidden" + websites when its parents weren't looking! +

+
+ + + diff --git a/requests/errors/default/404.http b/requests/errors/default/404.http new file mode 100644 index 0000000..8cb24e7 --- /dev/null +++ b/requests/errors/default/404.http @@ -0,0 +1,73 @@ +HTTP/1.1 404 Not Found +Cache-Control: no-cache +Connection: close +Content-Type: text/html + + + + + + + 404 Not Found + + + +
+

404 Not Found

+

Oops! The page you are looking for could not be found.

+
+
+

+ Why was the HTTP request so lonely? It kept getting "404 Not Found" + responses whenever it tried to connect! +

+
+ + + diff --git a/requests/errors/default/405.http b/requests/errors/default/405.http new file mode 100644 index 0000000..7d05862 --- /dev/null +++ b/requests/errors/default/405.http @@ -0,0 +1,73 @@ +HTTP/1.1 405 Method Not Allowed +Cache-Control: no-cache +Connection: close +Content-Type: text/html + + + + + + + 405 Method Not Allowed + + + +
+

405 Method Not Allowed

+

Oops! The method you used is not allowed for this resource.

+
+
+

+ Why did the developer break up with his Git repository? Because it had + too many "commits"ment issues! +

+
+ + + diff --git a/requests/errors/default/406.http b/requests/errors/default/406.http new file mode 100644 index 0000000..fa74f8c --- /dev/null +++ b/requests/errors/default/406.http @@ -0,0 +1,75 @@ +HTTP/1.1 406 Not Acceptable +Cache-Control: no-cache +Connection: close +Content-Type: text/html + + + + + + + 406 Not Acceptable + + + +
+

406 Not Acceptable

+

+ Oops! The server cannot produce a response that the client will accept. +

+
+
+

+ Why did the server break up with the client? They couldn't agree on + which language to speak! +

+
+ + + diff --git a/requests/errors/default/407.http b/requests/errors/default/407.http new file mode 100644 index 0000000..43ffa65 --- /dev/null +++ b/requests/errors/default/407.http @@ -0,0 +1,73 @@ +HTTP/1.1 407 Proxy Authentication Required +Cache-Control: no-cache +Connection: close +Content-Type: text/html + + + + + + + 407 Proxy Authentication Required + + + +
+

407 Proxy Authentication Required

+

Oops! Proxy authentication is required to access this resource.

+
+
+

+ Why was the proxy server so shy? It kept asking for authentication + before making friends! +

+
+ + + diff --git a/requests/errors/default/408.http b/requests/errors/default/408.http new file mode 100644 index 0000000..9fe1b1f --- /dev/null +++ b/requests/errors/default/408.http @@ -0,0 +1,73 @@ +HTTP/1.1 408 Request Timeout +Cache-Control: no-cache +Connection: close +Content-Type: text/html + + + + + + + 408 Request Timeout + + + +
+

408 Request Timeout

+

Oops! The server timed out waiting for the request.

+
+
+

+ Why did the computer apply for a job as a referee? It was great at + calling "timeout"! +

+
+ + + diff --git a/requests/errors/default/409.http b/requests/errors/default/409.http new file mode 100644 index 0000000..4c68ee9 --- /dev/null +++ b/requests/errors/default/409.http @@ -0,0 +1,73 @@ +HTTP/1.1 409 Conflict +Cache-Control: no-cache +Connection: close +Content-Type: text/html + + + + + + + 409 Conflict + + + +
+

409 Conflict

+

Oops! There was a conflict with the current state of the resource.

+
+
+

+ Why did the database refuse to go to therapy? It couldn't resolve its + "conflict" issues with the schema! +

+
+ + + diff --git a/requests/errors/default/410.http b/requests/errors/default/410.http new file mode 100644 index 0000000..d0637a8 --- /dev/null +++ b/requests/errors/default/410.http @@ -0,0 +1,75 @@ +HTTP/1.1 410 Gone +Cache-Control: no-cache +Connection: close +Content-Type: text/html + + + + + + + 410 Gone + + + +
+

410 Gone

+

+ Oops! The requested resource is no longer available and won't be back. +

+
+
+

+ Why did the website file for divorce? It was tired of being "gone" + without any notice! +

+
+ + + diff --git a/requests/errors/default/500.http b/requests/errors/default/500.http new file mode 100644 index 0000000..5dd868c --- /dev/null +++ b/requests/errors/default/500.http @@ -0,0 +1,73 @@ +HTTP/1.1 500 Internal Server Error +Cache-Control: no-cache +Connection: close +Content-Type: text/html + + + + + + + 500 Internal Server Error + + + +
+

500 Internal Server Error

+

Oops! Something went wrong on the server.

+
+
+

+ Why did the server go to therapy? It had too many internal issues it + couldn't resolve! +

+
+ + + diff --git a/requests/errors/default/501.http b/requests/errors/default/501.http new file mode 100644 index 0000000..7e14403 --- /dev/null +++ b/requests/errors/default/501.http @@ -0,0 +1,76 @@ +HTTP/1.1 501 Not Implemented +Cache-Control: no-cache +Connection: close +Content-Type: text/html + + + + + + + 501 Not Implemented + + + +
+

501 Not Implemented

+

+ Oops! The server does not support the functionality required to fulfill + the request. +

+
+
+

+ Why did the server break up with the developer? It couldn't implement + the changes requested! +

+
+ + + diff --git a/requests/errors/default/502.http b/requests/errors/default/502.http new file mode 100644 index 0000000..140d0c9 --- /dev/null +++ b/requests/errors/default/502.http @@ -0,0 +1,75 @@ +HTTP/1.1 502 Bad Gateway +Cache-Control: no-cache +Connection: close +Content-Type: text/html + + + + + + + 502 Bad Gateway + + + +
+

502 Bad Gateway

+

+ Oops! The server received an invalid response from an inbound server. +

+
+
+

+ Why did the server go to counseling? It couldn't find a good gateway to + communicate! +

+
+ + + diff --git a/requests/errors/default/503.http b/requests/errors/default/503.http new file mode 100644 index 0000000..d982dc1 --- /dev/null +++ b/requests/errors/default/503.http @@ -0,0 +1,70 @@ +HTTP/1.1 503 Service Unavailable +Cache-Control: no-cache +Connection: close +Content-Type: text/html + + + + + + + 503 Service Unavailable + + + +
+

503 Service Unavailable

+

Oops! The server is temporarily unable to handle the request.

+
+
+

Server status report: currently enjoying an extended coffee break!

+
+ + + diff --git a/requests/errors/default/504.http b/requests/errors/default/504.http new file mode 100644 index 0000000..34fbf99 --- /dev/null +++ b/requests/errors/default/504.http @@ -0,0 +1,76 @@ +HTTP/1.1 504 Gateway Timeout +Cache-Control: no-cache +Connection: close +Content-Type: text/html + + + + + + + 504 Gateway Timeout + + + +
+

504 Gateway Timeout

+

+ Oops! The server didn't receive a timely response from an upstream + server. +

+
+
+

+ Server timeout: It's like waiting for a bus in a town with no schedule – + you never know when it's coming! +

+
+ + + diff --git a/requests/errors/default/505.http b/requests/errors/default/505.http new file mode 100644 index 0000000..7902bb3 --- /dev/null +++ b/requests/errors/default/505.http @@ -0,0 +1,76 @@ +HTTP/1.1 505 HTTP Version Not Supported +Cache-Control: no-cache +Connection: close +Content-Type: text/html + + + + + + + 505 HTTP Version Not Supported + + + +
+

505 HTTP Version Not Supported

+

+ Oops! The server does not support the HTTP protocol version used in the + request. +

+
+
+

+ Attempting to connect? It's like trying to use a VHS tape in a Blu-ray + player – no support for the outdated format! +

+
+ + + diff --git a/requests/errors/proxy/400.http b/requests/errors/proxy/400.http new file mode 100644 index 0000000..78e0d5b --- /dev/null +++ b/requests/errors/proxy/400.http @@ -0,0 +1,73 @@ +HTTP/1.1 400 Bad Request +Cache-Control: no-cache +Connection: close +Content-Type: text/html + + + + + + + 400 Bad Request + + + +
+

400 Bad Request

+

Proxy Error

+

Oops! Something went wrong with your request.

+
+
+

+ Why did the server go broke? Because it couldn't process any requests! +

+
+ + + diff --git a/requests/errors/proxy/401.http b/requests/errors/proxy/401.http new file mode 100644 index 0000000..cdb8760 --- /dev/null +++ b/requests/errors/proxy/401.http @@ -0,0 +1,74 @@ +HTTP/1.1 401 Unauthorized +Cache-Control: no-cache +Connection: close +Content-Type: text/html + + + + + + + 401 Unauthorized + + + +
+

401 Unauthorized

+

Proxy Error

+

Oops! Access is denied. You are not authorized to view this page.

+
+
+

+ Why did the hacker break up with his computer? He found out it was + "encrypting" with someone else behind his back! +

+
+ + + diff --git a/requests/errors/proxy/402.http b/requests/errors/proxy/402.http new file mode 100644 index 0000000..1e40bfe --- /dev/null +++ b/requests/errors/proxy/402.http @@ -0,0 +1,74 @@ +HTTP/1.1 402 Payment Required +Cache-Control: no-cache +Connection: close +Content-Type: text/html + + + + + + + 402 Payment Required + + + +
+

402 Payment Required

+

Proxy Error

+

Oops! You need to pay to access this resource.

+
+
+

+ Why did the web developer always carry a credit card? To handle all + those "payment required" errors! +

+
+ + + diff --git a/requests/errors/proxy/403.http b/requests/errors/proxy/403.http new file mode 100644 index 0000000..1001570 --- /dev/null +++ b/requests/errors/proxy/403.http @@ -0,0 +1,74 @@ +HTTP/1.1 403 Forbidden +Cache-Control: no-cache +Connection: close +Content-Type: text/html + + + + + + + 403 Forbidden + + + +
+

403 Forbidden

+

Proxy Error

+

Oops! Access to this resource is forbidden.

+
+
+

+ Why did the computer get grounded? It kept accessing "forbidden" + websites when its parents weren't looking! +

+
+ + + diff --git a/requests/errors/proxy/404.http b/requests/errors/proxy/404.http new file mode 100644 index 0000000..f07e07d --- /dev/null +++ b/requests/errors/proxy/404.http @@ -0,0 +1,74 @@ +HTTP/1.1 404 Not Found +Cache-Control: no-cache +Connection: close +Content-Type: text/html + + + + + + + 404 Not Found + + + +
+

404 Not Found

+

Proxy Error

+

Oops! The page you are looking for could not be found.

+
+
+

+ Why was the HTTP request so lonely? It kept getting "404 Not Found" + responses whenever it tried to connect! +

+
+ + + diff --git a/requests/errors/proxy/405.http b/requests/errors/proxy/405.http new file mode 100644 index 0000000..dac455f --- /dev/null +++ b/requests/errors/proxy/405.http @@ -0,0 +1,74 @@ +HTTP/1.1 405 Method Not Allowed +Cache-Control: no-cache +Connection: close +Content-Type: text/html + + + + + + + 405 Method Not Allowed + + + +
+

405 Method Not Allowed

+

Proxy Error

+

Oops! The method you used is not allowed for this resource.

+
+
+

+ Why did the developer break up with his Git repository? Because it had + too many "commits"ment issues! +

+
+ + + diff --git a/requests/errors/proxy/406.http b/requests/errors/proxy/406.http new file mode 100644 index 0000000..7cc68c0 --- /dev/null +++ b/requests/errors/proxy/406.http @@ -0,0 +1,76 @@ +HTTP/1.1 406 Not Acceptable +Cache-Control: no-cache +Connection: close +Content-Type: text/html + + + + + + + 406 Not Acceptable + + + +
+

406 Not Acceptable

+

Proxy Error

+

+ Oops! The server cannot produce a response that the client will accept. +

+
+
+

+ Why did the server break up with the client? They couldn't agree on + which language to speak! +

+
+ + + diff --git a/requests/errors/proxy/407.http b/requests/errors/proxy/407.http new file mode 100644 index 0000000..7d11749 --- /dev/null +++ b/requests/errors/proxy/407.http @@ -0,0 +1,74 @@ +HTTP/1.1 407 Proxy Authentication Required +Cache-Control: no-cache +Connection: close +Content-Type: text/html + + + + + + + 407 Proxy Authentication Required + + + +
+

407 Proxy Authentication Required

+

Proxy Error

+

Oops! Proxy authentication is required to access this resource.

+
+
+

+ Why was the proxy server so shy? It kept asking for authentication + before making friends! +

+
+ + + diff --git a/requests/errors/proxy/408.http b/requests/errors/proxy/408.http new file mode 100644 index 0000000..9d4095a --- /dev/null +++ b/requests/errors/proxy/408.http @@ -0,0 +1,74 @@ +HTTP/1.1 408 Request Timeout +Cache-Control: no-cache +Connection: close +Content-Type: text/html + + + + + + + 408 Request Timeout + + + +
+

408 Request Timeout

+

Proxy Error

+

Oops! The server timed out waiting for the request.

+
+
+

+ Why did the computer apply for a job as a referee? It was great at + calling "timeout"! +

+
+ + + diff --git a/requests/errors/proxy/409.http b/requests/errors/proxy/409.http new file mode 100644 index 0000000..8e3ce35 --- /dev/null +++ b/requests/errors/proxy/409.http @@ -0,0 +1,74 @@ +HTTP/1.1 409 Conflict +Cache-Control: no-cache +Connection: close +Content-Type: text/html + + + + + + + 409 Conflict + + + +
+

409 Conflict

+

Proxy Error

+

Oops! There was a conflict with the current state of the resource.

+
+
+

+ Why did the database refuse to go to therapy? It couldn't resolve its + "conflict" issues with the schema! +

+
+ + + diff --git a/requests/errors/proxy/410.http b/requests/errors/proxy/410.http new file mode 100644 index 0000000..25f5d44 --- /dev/null +++ b/requests/errors/proxy/410.http @@ -0,0 +1,76 @@ +HTTP/1.1 410 Gone +Cache-Control: no-cache +Connection: close +Content-Type: text/html + + + + + + + 410 Gone + + + +
+

410 Gone

+

Proxy Error

+

+ Oops! The requested resource is no longer available and won't be back. +

+
+
+

+ Why did the website file for divorce? It was tired of being "gone" + without any notice! +

+
+ + + diff --git a/requests/errors/proxy/500.http b/requests/errors/proxy/500.http new file mode 100644 index 0000000..1a068b1 --- /dev/null +++ b/requests/errors/proxy/500.http @@ -0,0 +1,74 @@ +HTTP/1.1 500 Internal Server Error +Cache-Control: no-cache +Connection: close +Content-Type: text/html + + + + + + + 500 Internal Server Error + + + +
+

500 Internal Server Error

+

Proxy Error

+

Oops! Something went wrong on the server.

+
+
+

+ Why did the server go to therapy? It had too many internal issues it + couldn't resolve! +

+
+ + + diff --git a/requests/errors/proxy/501.http b/requests/errors/proxy/501.http new file mode 100644 index 0000000..d54ba94 --- /dev/null +++ b/requests/errors/proxy/501.http @@ -0,0 +1,77 @@ +HTTP/1.1 501 Not Implemented +Cache-Control: no-cache +Connection: close +Content-Type: text/html + + + + + + + 501 Not Implemented + + + +
+

501 Not Implemented

+

Proxy Error

+

+ Oops! The server does not support the functionality required to fulfill + the request. +

+
+
+

+ Why did the server break up with the developer? It couldn't implement + the changes requested! +

+
+ + + diff --git a/requests/errors/proxy/502.http b/requests/errors/proxy/502.http new file mode 100644 index 0000000..0fa7a12 --- /dev/null +++ b/requests/errors/proxy/502.http @@ -0,0 +1,76 @@ +HTTP/1.1 502 Bad Gateway +Cache-Control: no-cache +Connection: close +Content-Type: text/html + + + + + + + 502 Bad Gateway + + + +
+

502 Bad Gateway

+

Proxy Error

+

+ Oops! The server received an invalid response from an inbound server. +

+
+
+

+ Why did the server go to counseling? It couldn't find a good gateway to + communicate! +

+
+ + + diff --git a/requests/errors/proxy/503.http b/requests/errors/proxy/503.http new file mode 100644 index 0000000..92fbe21 --- /dev/null +++ b/requests/errors/proxy/503.http @@ -0,0 +1,71 @@ +HTTP/1.1 503 Service Unavailable +Cache-Control: no-cache +Connection: close +Content-Type: text/html + + + + + + + 503 Service Unavailable + + + +
+

503 Service Unavailable

+

Proxy Error

+

Oops! The server is temporarily unable to handle the request.

+
+
+

Server status report: currently enjoying an extended coffee break!

+
+ + + diff --git a/requests/errors/proxy/504.http b/requests/errors/proxy/504.http new file mode 100644 index 0000000..52a990a --- /dev/null +++ b/requests/errors/proxy/504.http @@ -0,0 +1,77 @@ +HTTP/1.1 504 Gateway Timeout +Cache-Control: no-cache +Connection: close +Content-Type: text/html + + + + + + + 504 Gateway Timeout + + + +
+

504 Gateway Timeout

+

Proxy Error

+

+ Oops! The server didn't receive a timely response from an upstream + server. +

+
+
+

+ Server timeout: It's like waiting for a bus in a town with no schedule – + you never know when it's coming! +

+
+ + + diff --git a/requests/errors/proxy/505.http b/requests/errors/proxy/505.http new file mode 100644 index 0000000..e3f52a3 --- /dev/null +++ b/requests/errors/proxy/505.http @@ -0,0 +1,77 @@ +HTTP/1.1 505 HTTP Version Not Supported +Cache-Control: no-cache +Connection: close +Content-Type: text/html + + + + + + + 505 HTTP Version Not Supported + + + +
+

505 HTTP Version Not Supported

+

Proxy Error

+

+ Oops! The server does not support the HTTP protocol version used in the + request. +

+
+
+

+ Attempting to connect? It's like trying to use a VHS tape in a Blu-ray + player – no support for the outdated format! +

+
+ + +