admin管理员组

文章数量:1125040

I'm working with two platforms, one of which is serving up a PNG image file, and the other is accessing image from a URL I send it. I'm not in control of the server or its headers, but I can see that the consuming platform is complaining about the content type:

Unexpected content-type: unsupported content-type: image/png; charset=UTF-8"

All I can assume is that it doesn't like ; charset=UTF-8 being tacked on the end. While I appreciate this is an odd thing to have against an image file, various browsers etc. have zero issues with it, nor do other platforms that request the file content.

Essentially I need to work out which of the two platforms is correct in order to raise a case, although I have already done so for the consumer because it seems some leniency here would make sense given the same URL works in other consumers.

Is this header valid, and should the consuming platform be dealing with it, or is the server in the wrong?

本文标签： Is quotContentType imagepng charsetUTF8quot a valid headerStack Overflow

版权声明：本文标题：Is "Content-Type: imagepng; charset=UTF-8" a valid header? - Stack Overflow 内容由网友自发贡献，该文观点仅代表作者本人， 转载请联系作者并注明出处：http://www.betaflare.com/web/1736631186a1945782.html， 本站仅提供信息存储空间服务，不拥有所有权，不承担相关法律责任。如发现本站有涉嫌抄袭侵权/违法违规的内容，一经查实，本站将立刻删除。