I noticed that Piwigo (tested on version 2.7.4) supplies an incorrect Content-Type header in its API responses. It says text/plain when it should be application/json.
When response is XML, the Content-Type needs to be application/xml.
Thank you.
I noticed that Piwigo (tested on version 2.7.4) supplies an incorrect Content-Type header in its API responses. It says text/plain when it should be _application/json_.
When response is XML, the Content-Type needs to be _application/xml_.
Thank you.
<!-- github-sync-id:128589295 -->
see pullrequest #510 for a fix in the json_encoder.
Concerning the XML API: RFC 2376 allows both application/xml and text/xml with the main difference being the allowed encoding (limited to Text encoding for text/xml)
see pullrequest #510 for a fix in the json_encoder.
Concerning the XML API: [RFC 2376](http://www.ietf.org/rfc/rfc2376.txt) allows both `application/xml` and `text/xml` with the main difference being the allowed encoding (limited to Text encoding for `text/xml`)
<!-- github-comment-id:235529507 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
I noticed that Piwigo (tested on version 2.7.4) supplies an incorrect Content-Type header in its API responses. It says text/plain when it should be application/json.
When response is XML, the Content-Type needs to be application/xml.
Thank you.
see pullrequest #510 for a fix in the json_encoder.
Concerning the XML API: RFC 2376 allows both
application/xmlandtext/xmlwith the main difference being the allowed encoding (limited to Text encoding fortext/xml)