Forum Discussion
The file itself is a financial transaction file so only a secure S3 seems to be acceptable by the client, however the HTTP Client does not support S3.
Thank you, I will look into the pipe.tmpDir suggestion. An alternative would be to create the file onto our groundplex which I believe the snap does support.
Ideally I would have liked to stream the $content but believe it is the filename attribute which is omitted by the snap when the option of 'TEXT' is selected that maybe the issue.
This is sample python code that looks to add the filename attribute within the boundary.
This might be a limitation of the HTTP Client or the endpoint we are using. I don't believe there is any reason why the filename attribute couldn't be added within the boundary if it were needed, but I am not strong on this topic so unsure.