Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We have a page on our intranet which is just plain/text encoded in UTF-8 and it contais insert scripts for database. And problem is, when I download this page to a file with wget or curl, my downloaded file has UTF-8 encoding but special characters(Czech language chars) are broken.

So where could be a problem?I can convert it to CP-1250 encoding which works fine(I also tried ISO8859-2, it doesn't work either), but I can't use it for db insert via SQL*Plus, because our DB is encoded in UTF-8.

Thanks a lot for answers

share|improve this question
I think your file is downloaded correctly. Nor the web server, nor wget, nor curl ever modify the files. So first check your file is okay on the web server and/or compare the checksum of the original file and the checksum of the downloaded file. – Gregory MOUSSAT Mar 16 '12 at 11:31
How did you check that the file is broken? (Which program / editor?) – Andreas Florath Mar 23 '12 at 17:31
@AndreasFlorath How did you solve this problem? – ANT Jun 17 '14 at 17:26

The HTTP protocol communicates in US_ASCII.

Therefore, plain/text content CAN NOT be UTF-8: it must be encoded if it contains non-ASCII UTF-8 characters.

share|improve this answer
Sorry - but this is complete nonsense: please consult RFC 2616, Section 3.6. – Andreas Florath Mar 23 '12 at 17:29
Transfer-coding ? How does that apply ? – adaptr Mar 23 '12 at 17:57
However, safe transport has a different focus for an 8bit-clean transfer protocol. RFC 2616, Section 3.6 – Andreas Florath Mar 23 '12 at 18:01

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.