amazon web services - AWS API Gateway to S3 - PUT Content-Encoding .Z Files -


i have run issue using api gateway proxy s3 (for custom authentication), in not handle binary data (which known issue).

i'm uploading either .gz or .z (unix compress utility) files. far understand it, data not maintained due encoding issues. can't seem figure out way decode data binary.

original leading bytes: \x1f\x8b\x08\x08\xb99\xbew\x00\x03

after passing through api gw: ��9�w�

... followed filename , rest of data.

one way of 'getting around this' specify content-encoding in header of put request api gw 'gzip'. seems force api gw decompress file before forwarding s3.

the same not work .z files compressed unix compress utility. should specify content-encoding 'compress'.

does have insight happening data, shed light on issue? also, know possible work-around's maintain encoding of data while passing through api gw (or decode once it's in s3)?

obviously access s3 api directly (or have api gw return pre-signed url accessing s3 api), there few reasons why don't want that.

i should mention don't understand @ encoding - sorry if there obvious answers of questions.

it's not "encoding issue" -- it's fact api gateway doesn't support binary data ("yet")... it's going potentially corrupt binary data, depending on specifics of data in question.

uploading content-encoding: gzip triggers decoding in front-end component is capable of dealing binary data (gzip, after all, standard encoding , binary) before passing request body core infrastructure... find workaround not consistently deliver correct results, depending on specific payload. fact works @ seems more bug feature.

for now, consistently viable option base64-encoding payload, increases size on-the-wire 33% (base64 encoding produces 4 bytes of output every 3 bytes of input) it's not of solution. base64 + gzip appropriate content-encoding: gzip should work, seems quite silly suggestion (converting compressed file base64 gzipping result try reduce size on wire) should consistent api gateway can deliver.


-

Comments

Post a Comment

Popular posts from this blog

amazon web services - S3 Pre-signed POST validate file type? -

i know it's possible put limit on file size content-length-range header. possible validate file type? https://docs.aws.amazon.com/amazons3/latest/dev/httppostforms.html#policyconditions i see there content-type header, if set say, audio/mp3 allow mp3 files , return error if file not mp3? i found previous question answers mention validating file size: s3 direct upload restricting file size , type you can specify content-type @ post request. you can specify @ signature, post must done content-type: { "expiration": "2007-12-01t12:00:00.000z", "conditions": [ {"acl": "public-read" }, {"bucket": "johnsmith" }, {"content-type: "audio/mp3"} ] } creating html form (using aws signature version 4) edit: @ previous question found, checking content-type.
Read more

c# - Check Keyboard Input Winforms -

i wondering if instead of doing this protected override void onkeydown(keyeventargs e) { if (e.keycode == keys.a) console.writeline("the key down."); } i set bool method , this: if(keydown(keys.a)) // whatever here i've been sitting here ages trying figure out how it. can't wrap head around it. in case wondering, plan call bool inside different method, check input. since want perform action after pressing key, using keydown event enough. but in cases suppose want check if specific key down in middle of process, can use getkeystate method way: [dllimport("user32.dll", charset = charset.auto, exactspelling = true)] public static extern short getkeystate(int keycode); public const int key_pressed = 0x8000; public static bool iskeydown(keys key) { return convert.toboolean(getkeystate((int)key) & key_pressed); } you should know, each time check key state using example iskeydown(keys.a) method returns true if ke...
Read more