-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
File getting corrupted with encrypt or sign true on Mac, Amazon Linux (maybe others too). #49
Comments
I have a mac and I have run it successfully there (same with EC2), please run django-pyas2 on both ends and let me know if the issue persists. |
@abhishek-ram Yeah, I used django-pyas2 on both ends (I have set up two instances of ubuntu & Amazon Linux to test the same). The ubuntu version works fine, I tested that with a few other as2 gateways as well. But the Amazon Linux version and two of my MacBooks have the issue. It works if I exclusively set the content type to binary. I can share access to these servers if you'd like to test it out. |
well, for binary files you are expected to set the content type to binary as we cannot detect it automatically |
Ah okay. I'm still wondering how it's working on an ubuntu server and not on others. Also, it works when using any other client to send. For example, I earlier used the windows client, Mendelson as2, to send files to django-pyas2 (on ubuntu) and it worked fine. The content-type was always the default, Please correct me if I'm wrong, the user who sends the file isn't explicitly selecting PS: I'm new to AS2 protocol, and am still exploring. Please excuse :) |
I tested the library on an ubuntu machine and everything worked well. But, then I tested the same on a mac and I got a corrupted file. The file size too was different. However, it works fine if I turn off the sign & encrypt options, or use content type binary. I've faced the same issue when I tested the same on an EC2 with Amazon Linux.
I've compared the binaries and t looks like the bytes are changing when decrypted.
And
.txt
or.csv
works in either case. The issue is when a more complex file is transferred, like apng
image or anxlsx
file.PS: I noticed #47 and it looks similar.
The text was updated successfully, but these errors were encountered: