HTTP error 431 after changing the server and IP of password authenticated domain Announcing...
Ring Automorphisms that fix 1.
Okay to merge included columns on otherwise identical indexes?
The logistics of corpse disposal
Generate an RGB colour grid
What's the purpose of writing one's academic biography in the third person?
What is the logic behind the Maharil's explanation of why we don't say שעשה ניסים on Pesach?
English words in a non-english sci-fi novel
What is Arya's weapon design?
Do I really need recursive chmod to restrict access to a folder?
Why did the Falcon Heavy center core fall off the ASDS OCISLY barge?
When were vectors invented?
What does the "x" in "x86" represent?
Why is "Consequences inflicted." not a sentence?
In predicate logic, does existential quantification (∃) include universal quantification (∀), i.e. can 'some' imply 'all'?
Why do people hide their license plates in the EU?
How discoverable are IPv6 addresses and AAAA names by potential attackers?
Seeking colloquialism for “just because”
How can I make names more distinctive without making them longer?
Is the Standard Deduction better than Itemized when both are the same amount?
Echoing a tail command produces unexpected output?
Output the ŋarâþ crîþ alphabet song without using (m)any letters
What is Wonderstone and are there any references to it pre-1982?
Novel: non-telepath helps overthrow rule by telepaths
How to deal with a team lead who never gives me credit?
HTTP error 431 after changing the server and IP of password authenticated domain
Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern)
Come Celebrate our 10 Year Anniversary!Hanging page loads every n loadsCache updates when migrating DNS from one provider to anotherPHP Files being cached by unknown entityNew server worked for a few hours, but now connections time outDebugging a timeout with ldap auth on apachePrevent browser URL from changing during page redirect in an SSL configuration using IBM HTTP server403 error after changing `DocumentRoot` to `/home/` subdirectoryFile uploads > 100KB hang with no apache errorsWrong(first/default) SSL certificate served Apache 2.4 - Ubuntu 18.04 muliple domain web serverERR_SSL_PROTOCOL_ERROR after http2 enabled
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
I have test domain eg: https:www.test.com, recently I have moved my server to new on which is hosted in liquid-web. After transferring this test account to new server and pointing, only this domain started throwing error HTTP error 431 and for some of them its blank screen. I have password authentication for this site.
When i open this in private window or after clearing cache, it is working fine. This problem now stopped all the server migration as we fear that this might effect our returning customers which is going to be big in number.
This is the screenshot I am getting. Tried removing htaccess, and put just index.html in the root, decreased TTL value, tried no-cache through meta tag in header, but nothing helped.
Anyone got insight on what is HTTP error 431
php ssl apache-2.4 cache
asked Feb 5 '18 at 8:44
jackjack
1013
add a comment |
I have test domain eg: https:www.test.com, recently I have moved my server to new on which is hosted in liquid-web. After transferring this test account to new server and pointing, only this domain started throwing error HTTP error 431 and for some of them its blank screen. I have password authentication for this site.
When i open this in private window or after clearing cache, it is working fine. This problem now stopped all the server migration as we fear that this might effect our returning customers which is going to be big in number.
This is the screenshot I am getting. Tried removing htaccess, and put just index.html in the root, decreased TTL value, tried no-cache through meta tag in header, but nothing helped.
Anyone got insight on what is HTTP error 431
php ssl apache-2.4 cache
asked Feb 5 '18 at 8:44
jackjack
1013
1
431 is a very specific error refering to the size of headers your client is sending "Request Headers Fields Too Large". Have you tried with a simple "curl" command if you reach the server successfully and/or reviewed the headers you are sending?
– ezra-s
Feb 5 '18 at 9:10
Still waiting to know what can cause issue in http 2.0
– jack
Apr 4 '18 at 17:05
add a comment |
I have test domain eg: https:www.test.com, recently I have moved my server to new on which is hosted in liquid-web. After transferring this test account to new server and pointing, only this domain started throwing error HTTP error 431 and for some of them its blank screen. I have password authentication for this site.
When i open this in private window or after clearing cache, it is working fine. This problem now stopped all the server migration as we fear that this might effect our returning customers which is going to be big in number.
This is the screenshot I am getting. Tried removing htaccess, and put just index.html in the root, decreased TTL value, tried no-cache through meta tag in header, but nothing helped.
Anyone got insight on what is HTTP error 431
php ssl apache-2.4 cache
asked Feb 5 '18 at 8:44
jackjack
1013
I have test domain eg: https:www.test.com, recently I have moved my server to new on which is hosted in liquid-web. After transferring this test account to new server and pointing, only this domain started throwing error HTTP error 431 and for some of them its blank screen. I have password authentication for this site.
When i open this in private window or after clearing cache, it is working fine. This problem now stopped all the server migration as we fear that this might effect our returning customers which is going to be big in number.
This is the screenshot I am getting. Tried removing htaccess, and put just index.html in the root, decreased TTL value, tried no-cache through meta tag in header, but nothing helped.
Anyone got insight on what is HTTP error 431
php ssl apache-2.4 cache
php ssl apache-2.4 cache
asked Feb 5 '18 at 8:44
jackjack
1013
asked Feb 5 '18 at 8:44
jackjack
1013
asked Feb 5 '18 at 8:44
jackjack
1013
asked Feb 5 '18 at 8:44
jackjack
1013
asked Feb 5 '18 at 8:44
jackjack
1013
1013
1
431 is a very specific error refering to the size of headers your client is sending "Request Headers Fields Too Large". Have you tried with a simple "curl" command if you reach the server successfully and/or reviewed the headers you are sending?
– ezra-s
Feb 5 '18 at 9:10
Still waiting to know what can cause issue in http 2.0
– jack
Apr 4 '18 at 17:05
add a comment |
1
431 is a very specific error refering to the size of headers your client is sending "Request Headers Fields Too Large". Have you tried with a simple "curl" command if you reach the server successfully and/or reviewed the headers you are sending?
– ezra-s
Feb 5 '18 at 9:10
Still waiting to know what can cause issue in http 2.0
– jack
Apr 4 '18 at 17:05
1
1
431 is a very specific error refering to the size of headers your client is sending "Request Headers Fields Too Large". Have you tried with a simple "curl" command if you reach the server successfully and/or reviewed the headers you are sending?
– ezra-s
Feb 5 '18 at 9:10
431 is a very specific error refering to the size of headers your client is sending "Request Headers Fields Too Large". Have you tried with a simple "curl" command if you reach the server successfully and/or reviewed the headers you are sending?
– ezra-s
Feb 5 '18 at 9:10
Still waiting to know what can cause issue in http 2.0
– jack
Apr 4 '18 at 17:05
Still waiting to know what can cause issue in http 2.0
– jack
Apr 4 '18 at 17:05
add a comment |
2 Answers
2
active
oldest
votes
After banging head on my desk several times, found out that issue happened as I was having large set of cookies created which I was using for saving customer visitor product id and this caused problem in HTTP 2.0 . I have rewritten the cookies to use only small space and now its working fine.
Site was not working even after i reduced the cookie site and uploaded the new code to new size. It was not accessing the site at all, I had to downgrade new server HTTP 2.0 to HTTP 1.2 which was working fine. Once we reduced the cookie size in the site, we have upgraded to HTTP 2.0 and it fixed the issue in new server.
But still not sure what triggered the problem in HTTP 2.0.
answered Mar 5 '18 at 8:44
jackjack
1013
add a comment |
We had same issue after upgrade to HTTP 2. It was caused by having too many cookies set. The tricky part is that this error was not caused by header field size (in Apache it is same for both HTTP 1 and 2). It was caused by large number of header fields. It seems HTTP 1 counts all cookies together as one header, but HTTP 2 counts each cookie as one header. After rising LimitRequestFields from 100 to 1000 problem disappeared.
answered 2 mins ago
Josef KejzlarJosef Kejzlar
1
New contributor
Josef Kejzlar is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
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%2f895662%2fhttp-error-431-after-changing-the-server-and-ip-of-password-authenticated-domain%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
After banging head on my desk several times, found out that issue happened as I was having large set of cookies created which I was using for saving customer visitor product id and this caused problem in HTTP 2.0 . I have rewritten the cookies to use only small space and now its working fine.
Site was not working even after i reduced the cookie site and uploaded the new code to new size. It was not accessing the site at all, I had to downgrade new server HTTP 2.0 to HTTP 1.2 which was working fine. Once we reduced the cookie size in the site, we have upgraded to HTTP 2.0 and it fixed the issue in new server.
But still not sure what triggered the problem in HTTP 2.0.
answered Mar 5 '18 at 8:44
jackjack
1013
add a comment |
After banging head on my desk several times, found out that issue happened as I was having large set of cookies created which I was using for saving customer visitor product id and this caused problem in HTTP 2.0 . I have rewritten the cookies to use only small space and now its working fine.
Site was not working even after i reduced the cookie site and uploaded the new code to new size. It was not accessing the site at all, I had to downgrade new server HTTP 2.0 to HTTP 1.2 which was working fine. Once we reduced the cookie size in the site, we have upgraded to HTTP 2.0 and it fixed the issue in new server.
But still not sure what triggered the problem in HTTP 2.0.
answered Mar 5 '18 at 8:44
jackjack
1013
add a comment |
After banging head on my desk several times, found out that issue happened as I was having large set of cookies created which I was using for saving customer visitor product id and this caused problem in HTTP 2.0 . I have rewritten the cookies to use only small space and now its working fine.
Site was not working even after i reduced the cookie site and uploaded the new code to new size. It was not accessing the site at all, I had to downgrade new server HTTP 2.0 to HTTP 1.2 which was working fine. Once we reduced the cookie size in the site, we have upgraded to HTTP 2.0 and it fixed the issue in new server.
But still not sure what triggered the problem in HTTP 2.0.
answered Mar 5 '18 at 8:44
jackjack
1013
After banging head on my desk several times, found out that issue happened as I was having large set of cookies created which I was using for saving customer visitor product id and this caused problem in HTTP 2.0 . I have rewritten the cookies to use only small space and now its working fine.
Site was not working even after i reduced the cookie site and uploaded the new code to new size. It was not accessing the site at all, I had to downgrade new server HTTP 2.0 to HTTP 1.2 which was working fine. Once we reduced the cookie size in the site, we have upgraded to HTTP 2.0 and it fixed the issue in new server.
But still not sure what triggered the problem in HTTP 2.0.
answered Mar 5 '18 at 8:44
jackjack
1013
answered Mar 5 '18 at 8:44
jackjack
1013
answered Mar 5 '18 at 8:44
jackjack
1013
answered Mar 5 '18 at 8:44
jackjack
1013
1013
add a comment |
add a comment |
We had same issue after upgrade to HTTP 2. It was caused by having too many cookies set. The tricky part is that this error was not caused by header field size (in Apache it is same for both HTTP 1 and 2). It was caused by large number of header fields. It seems HTTP 1 counts all cookies together as one header, but HTTP 2 counts each cookie as one header. After rising LimitRequestFields from 100 to 1000 problem disappeared.
answered 2 mins ago
Josef KejzlarJosef Kejzlar
1
New contributor
Josef Kejzlar is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
We had same issue after upgrade to HTTP 2. It was caused by having too many cookies set. The tricky part is that this error was not caused by header field size (in Apache it is same for both HTTP 1 and 2). It was caused by large number of header fields. It seems HTTP 1 counts all cookies together as one header, but HTTP 2 counts each cookie as one header. After rising LimitRequestFields from 100 to 1000 problem disappeared.
answered 2 mins ago
Josef KejzlarJosef Kejzlar
1
New contributor
Josef Kejzlar is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
We had same issue after upgrade to HTTP 2. It was caused by having too many cookies set. The tricky part is that this error was not caused by header field size (in Apache it is same for both HTTP 1 and 2). It was caused by large number of header fields. It seems HTTP 1 counts all cookies together as one header, but HTTP 2 counts each cookie as one header. After rising LimitRequestFields from 100 to 1000 problem disappeared.
answered 2 mins ago
Josef KejzlarJosef Kejzlar
1
New contributor
Josef Kejzlar is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
We had same issue after upgrade to HTTP 2. It was caused by having too many cookies set. The tricky part is that this error was not caused by header field size (in Apache it is same for both HTTP 1 and 2). It was caused by large number of header fields. It seems HTTP 1 counts all cookies together as one header, but HTTP 2 counts each cookie as one header. After rising LimitRequestFields from 100 to 1000 problem disappeared.
answered 2 mins ago
Josef KejzlarJosef Kejzlar
1
New contributor
Josef Kejzlar is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 2 mins ago
Josef KejzlarJosef Kejzlar
1
New contributor
Josef Kejzlar is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 2 mins ago
Josef KejzlarJosef Kejzlar
1
answered 2 mins ago
Josef KejzlarJosef Kejzlar
1
1
New contributor
Josef Kejzlar is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Josef Kejzlar is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Josef Kejzlar is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
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%2f895662%2fhttp-error-431-after-changing-the-server-and-ip-of-password-authenticated-domain%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
1
431 is a very specific error refering to the size of headers your client is sending "Request Headers Fields Too Large". Have you tried with a simple "curl" command if you reach the server successfully and/or reviewed the headers you are sending?
– ezra-s
Feb 5 '18 at 9:10
Still waiting to know what can cause issue in http 2.0
– jack
Apr 4 '18 at 17:05