Chrome - can't save settings "Please match the requested format"
-
Can't believe I am the only one with this problem but please let me know if I am…...
In several places in pfSense 2.3.2 I can't save changes when browsing with Chrome on Windows 7 (Version 53.0.2785.116 m)
If I make the exact same change in Firefox it saves fine - I am not making a mistake in the field like it suggests.
For example I try adding a domain override to DNS Resolver which I ended up doing in firefox with the same parameters as the screenshot, and it worked. But in Chrome it won't save. From several machines on the LAN. Is this only me?
-
You're not the only one with the issue. It's a known issue with Chrome. A patch has been created and will be applied to future versions of pfSense, and there are at least three other topics with this same issue.
Following the link above will take you to a post that contains info on how you can apply the patch to pfSense now, if you're daring enough to apply patches to your system. If you're not that daring, just use another browser instead of Chrome.
Edit: changed link to post
-
Thanks - oddly I did search the forum for Chrome and didn't see an obvious thread similar.
I guess it's comforting I am not the only one, although slightly ironic that I use firefox as my normal browser and was going to dedicate Chrome to just be my pfsense dashboard and editor! Now I will have to use Edge which doesn't make me happy….
-
huh? if firefox is your browser of choice why would you not use that to admin pfsense??
-
Thanks - oddly I did search the forum for Chrome and didn't see an obvious thread similar.
"Chome" is to generic. It customary to search for error messages themselves.
Also use advanced search with search order most recent first. The threads are there and near the top of results list.
-
A twist to this I've not seen mentioned yet so I'll do the honors.
This seems to only be an issue when the html form input tag value is not empty. Once populated with a value then the issue arises.
Set the value to an empty string (""; remove the 'x') and the first submission will work. But then value is no longer empty and any further attempt to submit a value will be rejected. Even though it matches the pattern.
Furthermore it appears that when value is empty the pattern check is not effective as it accepts anything. So it (Chrome pattern check) is even more broken that previously thought. It seems to just completely not work.
Can anyone verify this? My simplistic test case may have holes.
Version 53.0.2785.116 m (64-bit)
Google Chrome is up to date.Appling some additional patterns seem to indicate that only some characters can/cannot be escaped in a character class.
-
huh? if firefox is your browser of choice why would you not use that to admin pfsense??
Well as you asked…. I run daily with several dozen firefox tabs for my regular "work". I also have lots of other applications open. It was useful to have the pfsense dashboard and logs on a totally different browser so that I could quickly locate it on the taskbar. Actually I am still using it for this, but given the above am doing changes to config in firefox.
