dlna compliance issues mk2

We're failing another DLNA test (see text below). We're on cayenne.

Test: To verify that HTTP/1.1 client endpoints properly handle HTTP response codes of 1xx from HTTP servers, even when not expected.

8/06/2008 16:16:34: INFO: *** Starting Test: => "7.4.42.4 MT Baseline Transport: HTTP Client Endpoints: 1xx Status Codes"
18/06/2008 16:16:34: INFO: 1. Start a DMS Simulator with the name “7.4.42.4 DMS”.
18/06/2008 16:16:35: INFO: 2. Prompt the user to render/download a media item from the DMS Simulator.
18/06/2008 16:16:48: INFO: 3.1 Received an HTTP GET, checking its version to see if it is HTTP/1.1.
18/06/2008 16:16:48: INFO: 3.2 The request was found to be HTTP Version 1.1, sending the response using 100 continue.
18/06/2008 16:16:48: INFO: Now sending the 200 OK.
18/06/2008 16:16:48: INFO: 4. Please verify that the media item successfully rendered.
18/06/2008 16:17:44: INFO: DUT did not properly handle HTTP response codes of 1xx from HTTP servers.
18/06/2008 16:17:49: FAILED: DUT did not properly handle HTTP response codes of 1xx from HTTP servers.


There doesn't seem to be any handling of status code 100 in CHTTPFileObject::HandleHeaderRead. As far as I'm aware we should just ignore the 100 and wait for the next header to arrive. 

I tried adding this:

                switch(ulHTTPStatus)
                {
                    case 100: // Continue // XXX
                      retVal= HXR_OK; //XXX
                      break;      // XXX

                    case 206: // Success. Partial data.

but that doesn't seem to help. Any pointers on what we should be doing in response to a 100 status code ? I'm guessing it's an easy fix, but httpfsys is pretty big so any help much appreciated.

John








_______________________________________________
Helix-client-dev mailing list
[email protected]
http://lists.helixcommunity.org/mailman/listinfo/helix-client-dev