Welcome to the Cumulus Support forum.

Latest Cumulus MX V3 release 3.28.6 (build 3283) - 21 March 2024

Cumulus MX V4 beta test release 4.0.0 (build 4018) - 28 March 2024

Legacy Cumulus 1 release v1.9.4 (build 1099) - 28 November 2014 (a patch is available for 1.9.4 build 1099 that extends the date range of drop-down menus to 2030)

Download the Software (Cumulus MX / Cumulus 1 and other related items) from the Wiki

Character set translation error

Discussion of Ken True's web site templates

Moderator: saratogaWX

Post Reply
User avatar
N0BGS
Posts: 205
Joined: Sat 10 Nov 2012 2:26 am
Weather Station: Davis Vantage Pro 2
Operating System: Win10vm,VMWare ESXi 7.0
Location: Hermon, Maine USA
Contact:

Character set translation error

Post by N0BGS »

Hi Ken:

I recently updated to the current version of get-nnvl-iod.php and am now getting the following errors:

Code: Select all

Notice: iconv(): Wrong charset, conversion from `UTF-8 VIA: HTTP/1.1 SOPHOS.HTTP.PROXY:3128 CONNECTION: CLOSE' to `ISO-8859-1//TRANSLIT' is not allowed in /var/www/html/get-nnvl-iod.php on line 271

Notice: iconv(): Wrong charset, conversion from `UTF-8 VIA: HTTP/1.1 SOPHOS.HTTP.PROXY:3128 CONNECTION: CLOSE' to `ISO-8859-1//TRANSLIT' is not allowed in /var/www/html/get-nnvl-iod.php on line 272

Notice: iconv(): Wrong charset, conversion from `UTF-8 VIA: HTTP/1.1 SOPHOS.HTTP.PROXY:3128 CONNECTION: CLOSE' to `ISO-8859-1//TRANSLIT' is not allowed in /var/www/html/get-nnvl-iod.php on line 273
You can see this here: http://www.kpw3.com/wxnoaaiod.php

I do have a Sophos firewall but interestingly I get the identical error wording when I go to that page from the server loopback address, i.e. http://127.0.0.1/wxnoaaiod.php so the firewall shouldn't come into it at that point.

Any ideas?

Thanks,

--Kurt
Blitzortung Station 1809
User avatar
saratogaWX
Posts: 1170
Joined: Wed 06 May 2009 5:02 am
Weather Station: Davis Vantage Pro Plus
Operating System: Windows 10 Professional
Location: Saratoga, CA, USA
Contact:

Re: Character set translation error

Post by saratogaWX »

I think this is caused by a failure to parse the charset= info in the HTTP response headers.

Try changing

Code: Select all

preg_match('|charset="{0,1}([^"]+)"{0,1}|i',$headers,$matches);
to

Code: Select all

preg_match('|charset="{0,1}([^"\r]+)"{0,1}\r\n|is',$headers,$matches);
and see if that fixes the issue.

Best regards,
Ken
User avatar
N0BGS
Posts: 205
Joined: Sat 10 Nov 2012 2:26 am
Weather Station: Davis Vantage Pro 2
Operating System: Win10vm,VMWare ESXi 7.0
Location: Hermon, Maine USA
Contact:

Re: Character set translation error

Post by N0BGS »

That's done it, Ken. Sorry about my slow reply.

Thanks much,

--Kurt
Blitzortung Station 1809
Post Reply