search

OpenSocial / spec

OpenSocial Specification #social
http://opensocial.org/
Apache License 2.0
106 stars 11 forks source link

Orkut proxy not following charset information (makeRequest) #522

Closed mmarum-sugarcrm closed 11 years ago

mmarum-sugarcrm commented 11 years ago

Original author: vagalumeweb@gmail.com (August 20, 2008 18:49:17)

Description of the bug/feature ================================== Even if the third-party server provides the charset information, orkut's proxy ignores it and replies as utf-8.

PLEASE FILL OUT THE FOLLOWING FOR A BUG REPORT ONLY (delete everything below this line for a feature request):

What steps will reproduce the problem? ======================================

  1. Call http://vagalume.uol.com.br/opensocial/getinfo.php?type=basic&band_durl=u2&letra_durl=one from your browser and see ISO-8859-1 is provided as http header response.
  2. If you make the same call via makeRequest, it will ignore ISO-8859-1 and reply as UTF-8 3.

What is the expected output? ============================ Proxy charset should be the same as third-party server's charset. Same problem happens with main XML (charset provided inline). See http://vagalume.uol.com.br/opensocial/opensocial.xml

What is the actual output? ========================== UTF-8

Which container are you using? ============================== All (sandbox and production)

Which browsers have you experienced this on? ============================================ All

Which operating systems have you experienced this on? ===================================================== All

Please use labels and text to provide additional information.

Original issue: http://code.google.com/p/opensocial-resources/issues/detail?id=308

mmarum-sugarcrm commented 11 years ago

From api.kurrik%google.com@gtempaccount.com on September 03, 2008 20:36:21 The orkut proxy intentionally transcodes all incoming content to UTF-8, which is a superset of ISO-8859-1. This behavior is intentional.