[XERCESC-1805] Accessing the HTTP Content-Type

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.0.0
• Fix Version/s: 3.0.0
• Component/s: Miscellaneous
• Assignee: Boris Kolpackov
• Reporter: John Snelson
• Created: 15/May/08 15:13
• Updated: 09/Jul/08 16:01
• Resolved: 09/Jul/08 16:01

Description

A lot of algorithms need access to the HTTP "Content-Type" header, to decide how to parse a file, or what encoding it is in - for instance see XSLT 2.0's unparsed-text() function:

http://www.w3.org/TR/xslt20/#unparsed-text

We should add a method, BinInputStream::getContentType(), and implement it in the HTTP input stream implementations. The method should return 0 when the content type is not available, like for file input streams.

In addition, the socket and WinSock HTTP InputStream implementations have a number of problems:

1) They used fixed buffers which can result in buffer overflow.
2) They needlessly duplicate a whole load of code that could be shared.
3) They transcode to the local code page rather than "ISO8859-1".