When/why would Chrome get 500 error on localhost but load OK from 127.0.0.1, while Firefox loads both? ...
How does the math work when buying airline miles?
What does 丫 mean? 丫是什么意思？
What is best way to wire a ceiling receptacle in this situation?
Project Euler #1 in C++
How do I find out the mythology and history of my Fortress?
Maximum summed subsequences with non-adjacent items
Trademark violation for app?
Misunderstanding of Sylow theory
Sum letters are not two different
Is there hard evidence that the grant peer review system performs significantly better than random?
Can the Flaming Sphere spell be rammed into multiple Tiny creatures that are in the same 5-foot square?
Why does it sometimes sound good to play a grace note as a lead in to a note in a melody?
How would a mousetrap for use in space work?
Prove that BD bisects angle ABC
How did Fremen produce and carry enough thumpers to use Sandworms as de facto Ubers?
Putting class ranking in CV, but against dept guidelines
Output Devanagari (Hindi) from raw unicode using luatex
An adverb for when you're not exaggerating
Is it possible for SQL statements to execute concurrently within a single session in SQL Server?
Why is it faster to reheat something than it is to cook it?
How often does castling occur in grandmaster games?
Are sorcerers unable to use the Careful Spell metamagic option on themselves?
What order were files/directories output in dir?
What to do with repeated rejections for phd position
When/why would Chrome get 500 error on localhost but load OK from 127.0.0.1, while Firefox loads both?
Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 23, 2019 at 23:30 UTC (7:30pm US/Eastern)phpMyAdmin randomly shows blank content pages?localhost problem on my mamp serverCannot find local host via browser - can ping localhost and 127.0.0.1 okphpMyAdmin 3.4.4 install over MySQL 5.1 database with cookie authentication failsFirefox no longer loads javascript from localhostWhy is “localhost” slower than “127.0.0.1” in Google Chrome - Windows 8?Google Chrome can't access localhost domainsWhy is 50.22.53.71 hitting my localhost node.js in an attempt to find a php setupBlock chrome or firefox from accessing localhostFirefox loads, but won't load websites, after crash
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
So when/why would Chrome fail on localhost but load OK from 127.0.0.1?
PHP MySQL IIS Windows 10 was running just fine. phpMyAdmin suggested updating. So, renamed working directories to -old. Attempted to update phpMyAdmin and it needed to update PHP as well. Had issues (deprecated functions) so returned to using the original directories. Screwed something up I can't identify.
Yikes! Chrome will no longer load localhost/phpmyadmin/index.php
Error 500: The localhost page isn’t working. localhost is currently unable to handle this request.
NOPE! NOT a server error, because:
Firefox 50.1.0 DOES load phpMyAdmin index page correctly and run queries
Chrome 55.0.2883.87 m DOES load http://127.0.0.1/phpmyadmin/index.php correctly and run queries
Chrome also runs my own php application scripts that use MySQL just fine.
I given the directory phpMyAdmin directory every permission from any user including IIS_IUSRS. But since access Chrome from 127.0.0.1 works fine and Firefox works from localhost, I don't expect it to be a file permissions issue.
Following advice I found elsewhere, I've been to chrome://flag and reset to defaults.
I have cleared Chrome cache from 4 weeks before, up to now.
I hesitate to clear cookies in case of some I may need to keep to be recognized on other certain sites, etc. Not sure how to view and delete only phpMyAdmin related ones, if applicable.
I "think" I left config.inc.ini unchanged from when it was working. phpMyAdmin is all in wwwroot of inetpub.
Stop and Start MySQL service. Browser ctrl-shift-R reload. Fruitless. I suppose I can bookmark 127.0.0.1 instead, but I'd rather learn what's going on.
So what changed to cause my Chrome to now treat localhost (fails to load) differently from 127.0.0.1 (loads just fine)?
google-chrome firefox localhost phpmyadmin load
edited Dec 24 '16 at 23:30
Arjan
27.1k1065107
asked Dec 24 '16 at 14:41
SadJustSadSadJustSad
111
bumped to the homepage by Community♦ 7 hours ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
So when/why would Chrome fail on localhost but load OK from 127.0.0.1?
PHP MySQL IIS Windows 10 was running just fine. phpMyAdmin suggested updating. So, renamed working directories to -old. Attempted to update phpMyAdmin and it needed to update PHP as well. Had issues (deprecated functions) so returned to using the original directories. Screwed something up I can't identify.
Yikes! Chrome will no longer load localhost/phpmyadmin/index.php
Error 500: The localhost page isn’t working. localhost is currently unable to handle this request.
NOPE! NOT a server error, because:
Firefox 50.1.0 DOES load phpMyAdmin index page correctly and run queries
Chrome 55.0.2883.87 m DOES load http://127.0.0.1/phpmyadmin/index.php correctly and run queries
Chrome also runs my own php application scripts that use MySQL just fine.
I given the directory phpMyAdmin directory every permission from any user including IIS_IUSRS. But since access Chrome from 127.0.0.1 works fine and Firefox works from localhost, I don't expect it to be a file permissions issue.
Following advice I found elsewhere, I've been to chrome://flag and reset to defaults.
I have cleared Chrome cache from 4 weeks before, up to now.
I hesitate to clear cookies in case of some I may need to keep to be recognized on other certain sites, etc. Not sure how to view and delete only phpMyAdmin related ones, if applicable.
I "think" I left config.inc.ini unchanged from when it was working. phpMyAdmin is all in wwwroot of inetpub.
Stop and Start MySQL service. Browser ctrl-shift-R reload. Fruitless. I suppose I can bookmark 127.0.0.1 instead, but I'd rather learn what's going on.
So what changed to cause my Chrome to now treat localhost (fails to load) differently from 127.0.0.1 (loads just fine)?
google-chrome firefox localhost phpmyadmin load
edited Dec 24 '16 at 23:30
Arjan
27.1k1065107
asked Dec 24 '16 at 14:41
SadJustSadSadJustSad
111
bumped to the homepage by Community♦ 7 hours ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
So when/why would Chrome fail on localhost but load OK from 127.0.0.1?
PHP MySQL IIS Windows 10 was running just fine. phpMyAdmin suggested updating. So, renamed working directories to -old. Attempted to update phpMyAdmin and it needed to update PHP as well. Had issues (deprecated functions) so returned to using the original directories. Screwed something up I can't identify.
Yikes! Chrome will no longer load localhost/phpmyadmin/index.php
Error 500: The localhost page isn’t working. localhost is currently unable to handle this request.
NOPE! NOT a server error, because:
Firefox 50.1.0 DOES load phpMyAdmin index page correctly and run queries
Chrome 55.0.2883.87 m DOES load http://127.0.0.1/phpmyadmin/index.php correctly and run queries
Chrome also runs my own php application scripts that use MySQL just fine.
I given the directory phpMyAdmin directory every permission from any user including IIS_IUSRS. But since access Chrome from 127.0.0.1 works fine and Firefox works from localhost, I don't expect it to be a file permissions issue.
Following advice I found elsewhere, I've been to chrome://flag and reset to defaults.
I have cleared Chrome cache from 4 weeks before, up to now.
I hesitate to clear cookies in case of some I may need to keep to be recognized on other certain sites, etc. Not sure how to view and delete only phpMyAdmin related ones, if applicable.
I "think" I left config.inc.ini unchanged from when it was working. phpMyAdmin is all in wwwroot of inetpub.
Stop and Start MySQL service. Browser ctrl-shift-R reload. Fruitless. I suppose I can bookmark 127.0.0.1 instead, but I'd rather learn what's going on.
So what changed to cause my Chrome to now treat localhost (fails to load) differently from 127.0.0.1 (loads just fine)?
google-chrome firefox localhost phpmyadmin load
edited Dec 24 '16 at 23:30
Arjan
27.1k1065107
asked Dec 24 '16 at 14:41
SadJustSadSadJustSad
111
So when/why would Chrome fail on localhost but load OK from 127.0.0.1?
PHP MySQL IIS Windows 10 was running just fine. phpMyAdmin suggested updating. So, renamed working directories to -old. Attempted to update phpMyAdmin and it needed to update PHP as well. Had issues (deprecated functions) so returned to using the original directories. Screwed something up I can't identify.
Yikes! Chrome will no longer load localhost/phpmyadmin/index.php
Error 500: The localhost page isn’t working. localhost is currently unable to handle this request.
NOPE! NOT a server error, because:
Firefox 50.1.0 DOES load phpMyAdmin index page correctly and run queries
Chrome 55.0.2883.87 m DOES load http://127.0.0.1/phpmyadmin/index.php correctly and run queries
Chrome also runs my own php application scripts that use MySQL just fine.
I given the directory phpMyAdmin directory every permission from any user including IIS_IUSRS. But since access Chrome from 127.0.0.1 works fine and Firefox works from localhost, I don't expect it to be a file permissions issue.
Following advice I found elsewhere, I've been to chrome://flag and reset to defaults.
I have cleared Chrome cache from 4 weeks before, up to now.
I hesitate to clear cookies in case of some I may need to keep to be recognized on other certain sites, etc. Not sure how to view and delete only phpMyAdmin related ones, if applicable.
I "think" I left config.inc.ini unchanged from when it was working. phpMyAdmin is all in wwwroot of inetpub.
Stop and Start MySQL service. Browser ctrl-shift-R reload. Fruitless. I suppose I can bookmark 127.0.0.1 instead, but I'd rather learn what's going on.
So what changed to cause my Chrome to now treat localhost (fails to load) differently from 127.0.0.1 (loads just fine)?
google-chrome firefox localhost phpmyadmin load
google-chrome firefox localhost phpmyadmin load
edited Dec 24 '16 at 23:30
Arjan
27.1k1065107
asked Dec 24 '16 at 14:41
SadJustSadSadJustSad
111
edited Dec 24 '16 at 23:30
Arjan
27.1k1065107
asked Dec 24 '16 at 14:41
SadJustSadSadJustSad
111
edited Dec 24 '16 at 23:30
Arjan
27.1k1065107
edited Dec 24 '16 at 23:30
Arjan
27.1k1065107
edited Dec 24 '16 at 23:30
Arjan
27.1k1065107
27.1k1065107
asked Dec 24 '16 at 14:41
SadJustSadSadJustSad
111
asked Dec 24 '16 at 14:41
SadJustSadSadJustSad
111
asked Dec 24 '16 at 14:41
SadJustSadSadJustSad
111
111
bumped to the homepage by Community♦ 7 hours 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 hours ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
A 500 Internal Server Error indicates that Chrome does try to load the page and even gets a server response (being the 500 error). So, the server fails. It probably has some logs?
As cookies are stored per (sub-)domain, and localhost and 127.0.0.1 are different domains, my bet is that Chrome has an old cookie for localhost, which has not yet expired, but is somehow no longer valid.
Even if PHP and phpMyAdmin are backwards compatible (so would handle differences after upgrades), the troublesome cookie might have been created while you were testing the new PHP and new phpMyAdmin. And now that you reverted the upgrade either PHP or myPhpAdmin does not understand the newer format of the cookie or a session it refers to.
For sessions, a browser's session cookie holds an id which on the server refers to "serialized" PHP objects. So, maybe the serialization format has changed in newer versions of PHP, and the old PHP does not know how to handle the newer format.
For other cookies, maybe phpMyAdmin has stored serialized objects in the cookie directly, or in its database, or simply expects different data than it finds in the cookie.
To test the above:
To see if a session cookie is the culprit: restart Chrome and try again.
To see if a regular cookie is causing this without wiping it yet: try an incognito session, which does not send existing cookies to the server. If that works: clear the localhost cookies.
If this does not work, then you need to find the 500 error in the server's log.
answered Dec 25 '16 at 8:28
ArjanArjan
27.1k1065107
1
You solved it ! Thank you. Details : By the time I saw the reply, I had already restarted Chrome (and the computer) several times. The problem seemed to remain with only phpMyAdmin. I found only years-old logs; nothing anywhere near current. But the suggested incognito window loaded just fine. I followed the instructions to clear specifically the phpMyAdmin cookies (2) under localhost. Cut url from incognito window, closed it, pasted into normal window. Momentary shock at 500 error (cache?) which disappeared on refresh window. Back to normal. Thanks again.
– SadJustSad
Jan 2 '17 at 10:52
@SadJustSad So why haven't you marked this as the answer?
– Dave E
Aug 26 '17 at 6:18
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
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%2fsuperuser.com%2fquestions%2f1159862%2fwhen-why-would-chrome-get-500-error-on-localhost-but-load-ok-from-127-0-0-1-whi%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
A 500 Internal Server Error indicates that Chrome does try to load the page and even gets a server response (being the 500 error). So, the server fails. It probably has some logs?
As cookies are stored per (sub-)domain, and localhost and 127.0.0.1 are different domains, my bet is that Chrome has an old cookie for localhost, which has not yet expired, but is somehow no longer valid.
Even if PHP and phpMyAdmin are backwards compatible (so would handle differences after upgrades), the troublesome cookie might have been created while you were testing the new PHP and new phpMyAdmin. And now that you reverted the upgrade either PHP or myPhpAdmin does not understand the newer format of the cookie or a session it refers to.
For sessions, a browser's session cookie holds an id which on the server refers to "serialized" PHP objects. So, maybe the serialization format has changed in newer versions of PHP, and the old PHP does not know how to handle the newer format.
For other cookies, maybe phpMyAdmin has stored serialized objects in the cookie directly, or in its database, or simply expects different data than it finds in the cookie.
To test the above:
To see if a session cookie is the culprit: restart Chrome and try again.
To see if a regular cookie is causing this without wiping it yet: try an incognito session, which does not send existing cookies to the server. If that works: clear the localhost cookies.
If this does not work, then you need to find the 500 error in the server's log.
answered Dec 25 '16 at 8:28
ArjanArjan
27.1k1065107
1
You solved it ! Thank you. Details : By the time I saw the reply, I had already restarted Chrome (and the computer) several times. The problem seemed to remain with only phpMyAdmin. I found only years-old logs; nothing anywhere near current. But the suggested incognito window loaded just fine. I followed the instructions to clear specifically the phpMyAdmin cookies (2) under localhost. Cut url from incognito window, closed it, pasted into normal window. Momentary shock at 500 error (cache?) which disappeared on refresh window. Back to normal. Thanks again.
– SadJustSad
Jan 2 '17 at 10:52
@SadJustSad So why haven't you marked this as the answer?
– Dave E
Aug 26 '17 at 6:18
add a comment |
A 500 Internal Server Error indicates that Chrome does try to load the page and even gets a server response (being the 500 error). So, the server fails. It probably has some logs?
As cookies are stored per (sub-)domain, and localhost and 127.0.0.1 are different domains, my bet is that Chrome has an old cookie for localhost, which has not yet expired, but is somehow no longer valid.
Even if PHP and phpMyAdmin are backwards compatible (so would handle differences after upgrades), the troublesome cookie might have been created while you were testing the new PHP and new phpMyAdmin. And now that you reverted the upgrade either PHP or myPhpAdmin does not understand the newer format of the cookie or a session it refers to.
For sessions, a browser's session cookie holds an id which on the server refers to "serialized" PHP objects. So, maybe the serialization format has changed in newer versions of PHP, and the old PHP does not know how to handle the newer format.
For other cookies, maybe phpMyAdmin has stored serialized objects in the cookie directly, or in its database, or simply expects different data than it finds in the cookie.
To test the above:
To see if a session cookie is the culprit: restart Chrome and try again.
To see if a regular cookie is causing this without wiping it yet: try an incognito session, which does not send existing cookies to the server. If that works: clear the localhost cookies.
If this does not work, then you need to find the 500 error in the server's log.
answered Dec 25 '16 at 8:28
ArjanArjan
27.1k1065107
1
You solved it ! Thank you. Details : By the time I saw the reply, I had already restarted Chrome (and the computer) several times. The problem seemed to remain with only phpMyAdmin. I found only years-old logs; nothing anywhere near current. But the suggested incognito window loaded just fine. I followed the instructions to clear specifically the phpMyAdmin cookies (2) under localhost. Cut url from incognito window, closed it, pasted into normal window. Momentary shock at 500 error (cache?) which disappeared on refresh window. Back to normal. Thanks again.
– SadJustSad
Jan 2 '17 at 10:52
@SadJustSad So why haven't you marked this as the answer?
– Dave E
Aug 26 '17 at 6:18
add a comment |
A 500 Internal Server Error indicates that Chrome does try to load the page and even gets a server response (being the 500 error). So, the server fails. It probably has some logs?
As cookies are stored per (sub-)domain, and localhost and 127.0.0.1 are different domains, my bet is that Chrome has an old cookie for localhost, which has not yet expired, but is somehow no longer valid.
Even if PHP and phpMyAdmin are backwards compatible (so would handle differences after upgrades), the troublesome cookie might have been created while you were testing the new PHP and new phpMyAdmin. And now that you reverted the upgrade either PHP or myPhpAdmin does not understand the newer format of the cookie or a session it refers to.
For sessions, a browser's session cookie holds an id which on the server refers to "serialized" PHP objects. So, maybe the serialization format has changed in newer versions of PHP, and the old PHP does not know how to handle the newer format.
For other cookies, maybe phpMyAdmin has stored serialized objects in the cookie directly, or in its database, or simply expects different data than it finds in the cookie.
To test the above:
To see if a session cookie is the culprit: restart Chrome and try again.
To see if a regular cookie is causing this without wiping it yet: try an incognito session, which does not send existing cookies to the server. If that works: clear the localhost cookies.
If this does not work, then you need to find the 500 error in the server's log.
answered Dec 25 '16 at 8:28
ArjanArjan
27.1k1065107
A 500 Internal Server Error indicates that Chrome does try to load the page and even gets a server response (being the 500 error). So, the server fails. It probably has some logs?
As cookies are stored per (sub-)domain, and localhost and 127.0.0.1 are different domains, my bet is that Chrome has an old cookie for localhost, which has not yet expired, but is somehow no longer valid.
Even if PHP and phpMyAdmin are backwards compatible (so would handle differences after upgrades), the troublesome cookie might have been created while you were testing the new PHP and new phpMyAdmin. And now that you reverted the upgrade either PHP or myPhpAdmin does not understand the newer format of the cookie or a session it refers to.
For sessions, a browser's session cookie holds an id which on the server refers to "serialized" PHP objects. So, maybe the serialization format has changed in newer versions of PHP, and the old PHP does not know how to handle the newer format.
For other cookies, maybe phpMyAdmin has stored serialized objects in the cookie directly, or in its database, or simply expects different data than it finds in the cookie.
To test the above:
To see if a session cookie is the culprit: restart Chrome and try again.
To see if a regular cookie is causing this without wiping it yet: try an incognito session, which does not send existing cookies to the server. If that works: clear the localhost cookies.
If this does not work, then you need to find the 500 error in the server's log.
answered Dec 25 '16 at 8:28
ArjanArjan
27.1k1065107
answered Dec 25 '16 at 8:28
ArjanArjan
27.1k1065107
answered Dec 25 '16 at 8:28
ArjanArjan
27.1k1065107
answered Dec 25 '16 at 8:28
ArjanArjan
27.1k1065107
27.1k1065107
1
You solved it ! Thank you. Details : By the time I saw the reply, I had already restarted Chrome (and the computer) several times. The problem seemed to remain with only phpMyAdmin. I found only years-old logs; nothing anywhere near current. But the suggested incognito window loaded just fine. I followed the instructions to clear specifically the phpMyAdmin cookies (2) under localhost. Cut url from incognito window, closed it, pasted into normal window. Momentary shock at 500 error (cache?) which disappeared on refresh window. Back to normal. Thanks again.
– SadJustSad
Jan 2 '17 at 10:52
@SadJustSad So why haven't you marked this as the answer?
– Dave E
Aug 26 '17 at 6:18
add a comment |
1
You solved it ! Thank you. Details : By the time I saw the reply, I had already restarted Chrome (and the computer) several times. The problem seemed to remain with only phpMyAdmin. I found only years-old logs; nothing anywhere near current. But the suggested incognito window loaded just fine. I followed the instructions to clear specifically the phpMyAdmin cookies (2) under localhost. Cut url from incognito window, closed it, pasted into normal window. Momentary shock at 500 error (cache?) which disappeared on refresh window. Back to normal. Thanks again.
– SadJustSad
Jan 2 '17 at 10:52
@SadJustSad So why haven't you marked this as the answer?
– Dave E
Aug 26 '17 at 6:18
1
1
You solved it ! Thank you. Details : By the time I saw the reply, I had already restarted Chrome (and the computer) several times. The problem seemed to remain with only phpMyAdmin. I found only years-old logs; nothing anywhere near current. But the suggested incognito window loaded just fine. I followed the instructions to clear specifically the phpMyAdmin cookies (2) under localhost. Cut url from incognito window, closed it, pasted into normal window. Momentary shock at 500 error (cache?) which disappeared on refresh window. Back to normal. Thanks again.
– SadJustSad
Jan 2 '17 at 10:52
You solved it ! Thank you. Details : By the time I saw the reply, I had already restarted Chrome (and the computer) several times. The problem seemed to remain with only phpMyAdmin. I found only years-old logs; nothing anywhere near current. But the suggested incognito window loaded just fine. I followed the instructions to clear specifically the phpMyAdmin cookies (2) under localhost. Cut url from incognito window, closed it, pasted into normal window. Momentary shock at 500 error (cache?) which disappeared on refresh window. Back to normal. Thanks again.
– SadJustSad
Jan 2 '17 at 10:52
@SadJustSad So why haven't you marked this as the answer?
– Dave E
Aug 26 '17 at 6:18
@SadJustSad So why haven't you marked this as the answer?
– Dave E
Aug 26 '17 at 6:18
add a comment |
Thanks for contributing an answer to Super User!
- 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%2fsuperuser.com%2fquestions%2f1159862%2fwhen-why-would-chrome-get-500-error-on-localhost-but-load-ok-from-127-0-0-1-whi%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
