Diagnostic->File editor strange behavior
-
I have been playing around a bit with my pfsense box and had the need to edit some of the system files.
In particular I was using the file editor in the web interface to edit loader.conf. At next reboot none of my settings were used and I saw no error displayed. I thought I made a mistake and I saved an empty loader.conf.I opened the file in vi and I found all my settings there with a ^M appended at the end. If I remember correctly ^M is used to represent ASCII 0Dh (Windows CR). Interestingly having a CR at the end of the line rather than just LF was enough to invalidate the line by the loader, however without displaying a parsing error.
Once the ^M were deleted in vi and the file saved it worked as supposed.
I dont know if the editor can be set to just use LF rather than LF+CR to avoid the problem. -
IIRC, the browser itself is sending the ^M (if you edited it on Linux/Mac it probably wouldn't be there). Though it should be possible to code around that.
-
What browser are you using? I can't reproduce this in Firefox.
Looks like IE does this.
-
Should be fixed in new snapshots:
https://rcs.pfsense.org/projects/pfsense/repos/mainline/commits/1fa00d6d70b9891c89c76edd6ff6be4bb8968b9e
-
What browser are you using? I can't reproduce this in Firefox.
Looks like IE does this.
Surely I was editing with ie 8 on win7
