[AWS] Configure AWS to use only S206 with Content-Range and no multipart/byteranges

[David SAUVAGE - AdaLabs Ltd]

Pascal,

Le 12/10/2011 21:08, Pascal Obry a écrit :
> Do you think you can provide a self contained program that exhibit
> this issue? 

See project tarball attached. Please read
sources/duplicate_content_type_field.adb header that contain a small README

This code make AWS creating two Content-Type fields in the HTTP header,
see below :

$ ./duplicate_content_type_field
>Connection: Keep-Alive
>Accept: */*
>User-Agent: Fake bzr/2.3.4 (urllib)
>Host: localhost:8080
>Pragma: no-cache
>Cache-Control: max-age=0
>Range: bytes=0-41,245983-246264
>Accept-Encoding: deflate, gzip
>Accept-Language: fr, ru, us
Server/ uri file.pack
Server/ real file file.pack
>Date: Thu, 13 Oct 2011 06:20:26 GMT
>Server: AdaLabs Web Server
>Content-Type: application/octet-stream                                 
                 <----- 1
>Connection: keep-alive
>Last-Modified: Thu, 13 Oct 2011 10:17:03 GMT
>Accept-Ranges: bytes
>Content-Type: multipart/byteranges; boundary=aws_range_separator   <----- 2
>--aws_range_separator
(EE)Application/ Exception name: AWS.HEADERS.FORMAT_ERROR

Note : The exception appears in this case but not in the real issue.


Cheers,

--

David SAUVAGE

Software Agile Architect, Director
AdaLabs Ltd - Mauritius
http://adalabs.com
+230 428 18 32
skype sauvaged
BRN C10097052
VAT 27035043


-------------- next part --------------
A non-text attachment was scrubbed...
Name: duplicate_content_type_field.tar.gz
Type: application/x-gzip
Size: 2085 bytes
Desc: not available
Url : /pipermail/aws/attachments/20111013/d99bf059/attachment.bin