Nginx 444 error eqivalent in Apache?nginx HTTPS serving with same config as HTTPReply with 200 from Nginx...
Is divide-by-zero a security vulnerability?
Practical reasons to have both a large police force and bounty hunting network?
Does the in-code argument passing conventions used on PDP-11's have a name?
Is there a math expression equivalent to the conditional ternary operator?
Deal the cards to the players
How do you make a gun that shoots melee weapons and/or swords?
I can't die. Who am I?
Iron deposits mined from under the city
Do natural melee weapons (from racial traits) trigger Improved Divine Smite?
3.5% Interest Student Loan or use all of my savings on Tuition?
What does it mean when I add a new variable to my linear model and the R^2 stays the same?
Computing the volume of a simplex-like object with constraints
Should we avoid writing fiction about historical events without extensive research?
The Key to the Door
Why would the IRS ask for birth certificates or even audit a small tax return?
What can I do if someone tampers with my SSH public key?
Why is my explanation wrong?
Can a space-faring robot still function over a billion years?
The (Easy) Road to Code
Rationale to prefer local variables over instance variables?
The need of reserving one's ability in job interviews
Are small insurances worth it
Learning to quickly identify valid fingering for piano?
Replacing tantalum capacitor with ceramic capacitor for Op Amps
Nginx 444 error eqivalent in Apache?
nginx HTTPS serving with same config as HTTPReply with 200 from Nginx config without serving a filenginx send blank 200 responsesNginx Global Error Pagenginx reverse proxy cache revalivation errorNginx return 444 depending on upstream response codecurl 7.21 does not correctly call a host with a host header on https(nginx) Apache Forbidden error (at random): No error logsNginx proxy_pass issue - getting 404How can I debug SSL traffic between nginx and an Apache backend with a pre-master key?
Is there any way to produce same Nginx 444 error in apache.
Nginx
444--> Connection Closed Without Response.
I like this error since if anyone tries to CURL he gets an empty response, but not so in Apache.
nginx http apache2
bumped to the homepage by Community♦ 7 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
|
show 1 more comment
Is there any way to produce same Nginx 444 error in apache.
Nginx
444--> Connection Closed Without Response.
I like this error since if anyone tries to CURL he gets an empty response, but not so in Apache.
nginx http apache2
bumped to the homepage by Community♦ 7 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
Most likely with custom error responses: httpd.apache.org/docs/2.4/custom-error.html if I am not mistaken.
– David B.
Dec 23 '16 at 20:35
but not defined "how to create connection closed error"
– Amanat
Dec 23 '16 at 20:39
No, in that case you'd use:ErrorDocument 444 "Connection Closed Without Response"
– David B.
Dec 23 '16 at 20:42
You are not getting my point sir. For example here is the IP with NGINX 444 error. 95.211.150.66. But with your solution users will read a text which i don't want to show.
– Amanat
Dec 23 '16 at 20:45
As far as I know, Apache doesn't have the equal functionality to the nginx 444 "error code". It is not an HTTP actual error code but an immediate shutdown of TCP connection.
– Tero Kilkanen
Jun 8 '17 at 11:59
|
show 1 more comment
Is there any way to produce same Nginx 444 error in apache.
Nginx
444--> Connection Closed Without Response.
I like this error since if anyone tries to CURL he gets an empty response, but not so in Apache.
nginx http apache2
Is there any way to produce same Nginx 444 error in apache.
Nginx
444--> Connection Closed Without Response.
I like this error since if anyone tries to CURL he gets an empty response, but not so in Apache.
nginx http apache2
nginx http apache2
edited Dec 23 '16 at 16:37
Machavity
570517
570517
asked Dec 23 '16 at 15:39
AmanatAmanat
373
373
bumped to the homepage by Community♦ 7 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 7 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
Most likely with custom error responses: httpd.apache.org/docs/2.4/custom-error.html if I am not mistaken.
– David B.
Dec 23 '16 at 20:35
but not defined "how to create connection closed error"
– Amanat
Dec 23 '16 at 20:39
No, in that case you'd use:ErrorDocument 444 "Connection Closed Without Response"
– David B.
Dec 23 '16 at 20:42
You are not getting my point sir. For example here is the IP with NGINX 444 error. 95.211.150.66. But with your solution users will read a text which i don't want to show.
– Amanat
Dec 23 '16 at 20:45
As far as I know, Apache doesn't have the equal functionality to the nginx 444 "error code". It is not an HTTP actual error code but an immediate shutdown of TCP connection.
– Tero Kilkanen
Jun 8 '17 at 11:59
|
show 1 more comment
Most likely with custom error responses: httpd.apache.org/docs/2.4/custom-error.html if I am not mistaken.
– David B.
Dec 23 '16 at 20:35
but not defined "how to create connection closed error"
– Amanat
Dec 23 '16 at 20:39
No, in that case you'd use:ErrorDocument 444 "Connection Closed Without Response"
– David B.
Dec 23 '16 at 20:42
You are not getting my point sir. For example here is the IP with NGINX 444 error. 95.211.150.66. But with your solution users will read a text which i don't want to show.
– Amanat
Dec 23 '16 at 20:45
As far as I know, Apache doesn't have the equal functionality to the nginx 444 "error code". It is not an HTTP actual error code but an immediate shutdown of TCP connection.
– Tero Kilkanen
Jun 8 '17 at 11:59
Most likely with custom error responses: httpd.apache.org/docs/2.4/custom-error.html if I am not mistaken.
– David B.
Dec 23 '16 at 20:35
Most likely with custom error responses: httpd.apache.org/docs/2.4/custom-error.html if I am not mistaken.
– David B.
Dec 23 '16 at 20:35
but not defined "how to create connection closed error"
– Amanat
Dec 23 '16 at 20:39
but not defined "how to create connection closed error"
– Amanat
Dec 23 '16 at 20:39
No, in that case you'd use:
ErrorDocument 444 "Connection Closed Without Response"
– David B.
Dec 23 '16 at 20:42
No, in that case you'd use:
ErrorDocument 444 "Connection Closed Without Response"
– David B.
Dec 23 '16 at 20:42
You are not getting my point sir. For example here is the IP with NGINX 444 error. 95.211.150.66. But with your solution users will read a text which i don't want to show.
– Amanat
Dec 23 '16 at 20:45
You are not getting my point sir. For example here is the IP with NGINX 444 error. 95.211.150.66. But with your solution users will read a text which i don't want to show.
– Amanat
Dec 23 '16 at 20:45
As far as I know, Apache doesn't have the equal functionality to the nginx 444 "error code". It is not an HTTP actual error code but an immediate shutdown of TCP connection.
– Tero Kilkanen
Jun 8 '17 at 11:59
As far as I know, Apache doesn't have the equal functionality to the nginx 444 "error code". It is not an HTTP actual error code but an immediate shutdown of TCP connection.
– Tero Kilkanen
Jun 8 '17 at 11:59
|
show 1 more comment
2 Answers
2
active
oldest
votes
444 is not returned to the client, it is only written into nginx logs signalling that a connection was closed with no response. This same firewall-like behavior can be achieved in apache using modsecurity and DROP actions.
add a comment |
Custom, non-standard HTTP response codes such as 444 do not seem to be supported by Apache.
I could not find an exhaustive list of allowed codes in Apache's documentation for the ErrorDocument directive, however testing with something like
<Location /444>
ErrorDocument 444 "Something"
</Location>
Doesn't even allow Apache to load, whereas changing the 444
above to 404
allows Apache to load without any errors or problems.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "2"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f822484%2fnginx-444-error-eqivalent-in-apache%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
444 is not returned to the client, it is only written into nginx logs signalling that a connection was closed with no response. This same firewall-like behavior can be achieved in apache using modsecurity and DROP actions.
add a comment |
444 is not returned to the client, it is only written into nginx logs signalling that a connection was closed with no response. This same firewall-like behavior can be achieved in apache using modsecurity and DROP actions.
add a comment |
444 is not returned to the client, it is only written into nginx logs signalling that a connection was closed with no response. This same firewall-like behavior can be achieved in apache using modsecurity and DROP actions.
444 is not returned to the client, it is only written into nginx logs signalling that a connection was closed with no response. This same firewall-like behavior can be achieved in apache using modsecurity and DROP actions.
answered May 23 '18 at 2:26
Jonah BentonJonah Benton
1,101312
1,101312
add a comment |
add a comment |
Custom, non-standard HTTP response codes such as 444 do not seem to be supported by Apache.
I could not find an exhaustive list of allowed codes in Apache's documentation for the ErrorDocument directive, however testing with something like
<Location /444>
ErrorDocument 444 "Something"
</Location>
Doesn't even allow Apache to load, whereas changing the 444
above to 404
allows Apache to load without any errors or problems.
add a comment |
Custom, non-standard HTTP response codes such as 444 do not seem to be supported by Apache.
I could not find an exhaustive list of allowed codes in Apache's documentation for the ErrorDocument directive, however testing with something like
<Location /444>
ErrorDocument 444 "Something"
</Location>
Doesn't even allow Apache to load, whereas changing the 444
above to 404
allows Apache to load without any errors or problems.
add a comment |
Custom, non-standard HTTP response codes such as 444 do not seem to be supported by Apache.
I could not find an exhaustive list of allowed codes in Apache's documentation for the ErrorDocument directive, however testing with something like
<Location /444>
ErrorDocument 444 "Something"
</Location>
Doesn't even allow Apache to load, whereas changing the 444
above to 404
allows Apache to load without any errors or problems.
Custom, non-standard HTTP response codes such as 444 do not seem to be supported by Apache.
I could not find an exhaustive list of allowed codes in Apache's documentation for the ErrorDocument directive, however testing with something like
<Location /444>
ErrorDocument 444 "Something"
</Location>
Doesn't even allow Apache to load, whereas changing the 444
above to 404
allows Apache to load without any errors or problems.
answered Jan 10 '18 at 11:22
jolianjolian
875
875
add a comment |
add a comment |
Thanks for contributing an answer to Server Fault!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f822484%2fnginx-444-error-eqivalent-in-apache%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Most likely with custom error responses: httpd.apache.org/docs/2.4/custom-error.html if I am not mistaken.
– David B.
Dec 23 '16 at 20:35
but not defined "how to create connection closed error"
– Amanat
Dec 23 '16 at 20:39
No, in that case you'd use:
ErrorDocument 444 "Connection Closed Without Response"
– David B.
Dec 23 '16 at 20:42
You are not getting my point sir. For example here is the IP with NGINX 444 error. 95.211.150.66. But with your solution users will read a text which i don't want to show.
– Amanat
Dec 23 '16 at 20:45
As far as I know, Apache doesn't have the equal functionality to the nginx 444 "error code". It is not an HTTP actual error code but an immediate shutdown of TCP connection.
– Tero Kilkanen
Jun 8 '17 at 11:59