[ 
https://issues.apache.org/jira/browse/XERCESC-2183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16991796#comment-16991796
 ] 

Scott Cantor commented on XERCESC-2183:
---------------------------------------

You should NOT be relying on Xerces for any networking. One semi-acceptable 
option might be the curl support, but if that's not sufficient, you should 
implement your own NetAccessor. The code inside the project now is a toy only 
and is not suitable for anything substantive.

Of course, most XML applications should NEVER allow any remote access to 
resources anyway, which is why this is not usually a major concern.

> Xerces block on socket receive
> ------------------------------
>
>                 Key: XERCESC-2183
>                 URL: https://issues.apache.org/jira/browse/XERCESC-2183
>             Project: Xerces-C++
>          Issue Type: Bug
>          Components: Utilities
>    Affects Versions: 3.2.1
>         Environment: Windows
> Visual Studio2017
>            Reporter: ayoub serti
>            Priority: Major
>              Labels: easyfix, windows
>
> Hello,
> We use Xerces to parse and validating xml data.
> When XML data contains external prolog ( web-hosted prolog ) like: 
> [http://www.w3.org/TR/html4/loose.dtd]
> Our application hang on BinHTTPURLInputStream::receive(char *buf, XMLSize_t 
> len) because it try to read 1024 bytes from socket without timeout.
> After investigation, We found that [http://www.w3.org/TR/html4/loose.dtd] 
> return a 307 status and ask browser to redirect to https url.
> I believe the simplest approach is to change buffer chunck size in 
> BinHTTPInputStreamCommon::sendRequest() : L223 to read only first part of 
> HTTP headers.
> Is there any way to configure socket timeout?



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org
For additional commands, e-mail: c-dev-h...@xerces.apache.org

Reply via email to