[ 
https://issues.apache.org/jira/browse/HTTPCORE-137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12557296#action_12557296
 ] 

Roland Weber commented on HTTPCORE-137:
---------------------------------------

Your PUT clients are obviously sending a HEAD request _before_ the PUT request, 
probably to verify that the resource to put doesn't exist yet. I suggest you 
handle the HEAD request as the HEAD request that it is, and then wait for the 
subsequent PUT request.


> Problem handling HTTP PUT requests 
> -----------------------------------
>
>                 Key: HTTPCORE-137
>                 URL: https://issues.apache.org/jira/browse/HTTPCORE-137
>             Project: HttpComponents Core
>          Issue Type: Bug
>          Components: HttpCore NIO
>    Affects Versions: 4.0-rc1
>         Environment: Java JDK 1.6.0_03 on Windows XP Service Pack 2
>            Reporter: Ronald E Johnson
>         Attachments: TestHTTPServer.java
>
>
> I have a Java Swing application with an HttpServer() instance running in a 
> SwingWorker thread.  I'm able to get at the HTTP GET requests by casting the 
> request as follows:
> if (request instanceof HttpEntityEnclosingRequest)  {
>             HttpEntity entity = ((HttpEntityEnclosingRequest) 
> request).getEntity();
>             byte[] entityContent = EntityUtils.toByteArray(entity);
>             logger.info("Incoming entity content (bytes): " + 
> entityContent.length);
> }
> However this does not work for PUT requests. In fact printing out the request 
> line of a PUT request appears as: "HEAD /test.txt HTTP/1.1", and I don't see 
> PUT in the request line at all.  Attempting to cast this as an 
> HttpEntityEnclosingRequest fails, and thus I'm not able to get at the 
> HttpEntity.  Is this functionality supported?  

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to