Databases
StackOverflow2013
Postsdbo
PODetecting the character encoding of an HTTP POST request
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PODetecting the character encoding of an HTTP POST request
    primarykey
    data
    text
    <p>I'm building a web service and have a node that accepts a POST to create a new resource. The resource expects one of two content-types - an XML format I'll be defining, or form-encoded variables.</p> <p>The idea is that consuming applications can POST XML directly and benefit from better validation etc., but there's also an HTML interface that will POST the form-encoded stuff. Obviously the XML format has a charset declaration, but I can't see how I detect the form's charset just from looking at the POST.</p> <p>A typical post to the form from Firefox looks like this:</p> <pre><code>POST /path HTTP/1.1 Host: www.myhostname.com User-Agent: Mozilla/5.0 [...etc...] Accept: text/html,application/xhtml+xml, [...etc...] Accept-Language: en-gb,en;q=0.5 Accept-Encoding: gzip,deflate Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 Keep-Alive: 300 Connection: keep-alive Content-Type: application/x-www-form-urlencoded Content-Length: 41 field1=value1&amp;field2=value2&amp;field3=value3 </code></pre> <p>Which doesn't seem to contain any useful indication of the character set.</p> <p>From what I can see, the application/x-www-form-urlencoded type is entirely defined in HTML, which just lays out the %-encoding rules, but doesn't say anything about what charset the data should be in.</p> <p>Basically, is there any way of telling the character set if I don't know the character set the HTML originally presented was? Otherwise I'll have to try and guess the character set based on what chars are present, and that's always a bit iffy from what I can tell.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USbignose
    1. USCiaran McNulty
    plurals
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    3. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PODetecting the character encoding of an HTTP POST request
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PODetecting the character encoding of an HTTP POST request
      1. USBuddy
      1. VTFavorite
    3. VO
      singulars
      1. PODetecting the character encoding of an HTTP POST request
      1. USSenthil Kumaran
      1. VTFavorite
    1. COThere are many subtleties here and behavior will vary by browser and operating system. One convention used by IE is that if you have a hidden INPUT with the name `_charset_`, IE will fill in that field with the character set it used when submitting the form. See also related question http://stackoverflow.com/questions/12830546/accept-charset-utf-8-parameter-doesnt-do-anything-when-used-in-form
      singulars
      1. PODetecting the character encoding of an HTTP POST request
      1. USEricLaw
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload