Special/accented characters not displaying - PFSense 2.3



  • Hello!

    I recently updated pfsense from 2.2.6 to 2.3. After that, special or accented characters in my captive portal page stopped displaying correctly. They show up as question marks. I have been reading about this, and already confirmed that the line is included in the code. If I take the same html file and uploaded to a pfsense 2.2.6 it will display correctly, and they issue will only occur when using it on a 2.3 installation. Also, if I open the file directly in any browser (IE, Chrome, Firefox) it also displays correctly.

    I attach the html file compressed to zip, as well as a couple of images to show the before and after.

    Thanks in advance for all the help you may provide and please let me know if there is any other info I should include.

    ![Before upgrade.png](/public/imported_attachments/1/Before upgrade.png)
    ![Before upgrade.png_thumb](/public/imported_attachments/1/Before upgrade.png_thumb)
    ![After upgrade.PNG](/public/imported_attachments/1/After upgrade.PNG)
    ![After upgrade.PNG_thumb](/public/imported_attachments/1/After upgrade.PNG_thumb)
    portal.zip


  • Rebel Alliance Developer Netgate

    Can you check the response headers from a browser in debug mode to see if perhaps there is some other difference? 2.2.x used lighttpd, 2.3 uses nginx, it's possible there is something in the HTTP headers making the browser interpret things differently.



  • Hi! Thanks for replying.

    Do you mean something like the attached image? I used firefox to display de captive portal and looked for the debugger option, but only the inspector tab showed me info. Te debugger one only said "this page doesn't have sources".



  • Rebel Alliance Developer Netgate

    Click the Network tab there, and then click on the GET for the portal file, and then look at the headers on the right, specifically all of the "response headers"



  • Hi!

    I got this information in the network tab.



  • Rebel Alliance Developer Netgate

    Now do the same against it on 2.2.x and compare :-)


Log in to reply