Unsolved
This post is more than 5 years old
1 Message
0
2697
Possibly an Atmos bug?
I've only been able to reproduce this on a specific file. I don't really want to post it on here, but I can email it if I need to for those that want to do testing. I'm uploading a compressed file via atmos_c (curl). Every file works as expected except for the one in question. When I retrieve the file back from the server is has the following text prepended to the data:
Here is the offending incoming header/bad data:
Server: nginx
Date: Mon, 13 Sep 2010 20:33:56 GMT
Content-Type: application/octet-stream
Transfer-Encoding: chunked
Connection: keep-alive
x-emc-policy: Plus
x-emc-listable-meta: x-uid=1000, x-gid=100, x-permissions=33188, x-compression=1
x-emc-meta: atime=2010-09-13T20:09:18Z, mtime=2010-09-13T20:09:18Z, ctime=2010-0
9-13T20:09:18Z, itime=2010-09-13T20:05:42Z, type=regular, uid= , gid=apach
e, objectid=4b0ab729a1230da704b0abf13c86de04c8e841637bb5, objname= , size
=4701488, nlink=1, policyname=Plus
x-emc-useracl: 4015050=FULL_CONTROL
x-emc-groupacl: other=NONE
Transfer-Encoding: chunked
da6
100000
scot4
18 Posts
0
September 13th, 2010 18:00
You could try putting the object in question up using AtmosFox http://www.suchisoft.com/atmosfox/AtmosFox.xpi or the simple obect Browser
https://community.emc.com/docs/DOC-509to (hopefully) narrow down the issue.you can also send me the object in question at junkin_scot [ at ] emc.com and I can look into it
hdawood
3 Posts
0
September 24th, 2010 07:00
I am interested in the compressed file if you don't mind sharing it. I have a virtual environment setup so it's easy to see what happens on both ends of the spectrum (sending and receiving).