The important parts of the response header coming from pfSense: Looking at the headers being sent and received, on the original POST occurring when the login form Sign In button is pressed, the result is a 302 redirect to / (root), with a new cookies being set. Why it's happening: It's a cookie problem, and it looks like it's a Chrome cookie problem. To recap: When logging in, the user is redirected back to the login page. Firefox and Edge (shudder) work just fine. I am experiencing this EXACT issue on EVERY Chrome browser I have tried. Would appreciate any tips if someone has one while I wait for this problem to occur again. Whereas with Firefox (Or a incognito Chrome session), I see:Ĭookie_test=1409391955 PHPSESSID=df69291fcaa88d76a0bed7862c3bed72Ģnd Edit: I've now cleared cache once again, and uninstalled/reinstalled Chrome. Upon doing some inspection with Fiddler, it looks like my Chrome install is doing something odd with cookies. but I'll take anything I can get at this point. I can give someone a username if they'd like to help figure this out. And switching certificates from my wildcard to the self signed that the install comes with makes no difference. 24 beta-m (64-bit) but it also happens on my Mac, and on my work laptop as well. I've run into it once or twice in Firefox, but restarting the browser fixed it there. Looks like the lighttpd.log is binary, so I can't read that… Is there some sort of logs I can look at on the backend to try to debug this problem? I'm about ready to pull my hair out. And it wouldn't be so bad if it was just on one computer. So I've now run into the same issue with another pfsense installation in Chrome as well.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |