Re: Decode umlauts on CGI-parameters

The encoding that gets sent by the browser to the server depends on the encoding of your web page and the browser. Ideally, you have both, a Content-Type: header specifying the character set and a <meta http-equiv="content-type" content="text/html; charset=utf-8"> element in your HTML.

Note that in my experience, at least Internet Explorer (6) does not send the value of an <input> button but only the name (I think).

Comment on Re: Decode umlauts on CGI-parameters Select or Download Code

Replies are listed 'Best First'.

Re^2: Decode umlauts on CGI-parameters
by Yaerox (Scribe) on Jul 16, 2015 at 08:33 UTC

<meta charset="UTF-8">

Update:

print "Content-type: text/html\n\n";
print "<html><head><meta charset=\"UTF-8\"></head>";
print "p_sAction: #" . $p_sAction . "#<br>";
[download]

this script won't print anything

I got some comparism on this script like the following

if ( $p_sAction eq $aText{'1460'} ){ } else { }
[download]

And this doesn't match. $aText is coming out of my DB where I save data uri-escaped, and return it unescaped.

Update 2:

# Benutzer löschen
print "#$p_sAction# eq #$aText{'1530'}#<br>";
if ( $p_sAction eq $aText{'1530'} ){
  print "HELLO WORLD<br>";
}
[download]

#Benutzer löschen# eq #Benutzer löschen#

[reply]
[d/l]
[select]


Perl-Sensitive Sunglasses
	PerlMonks