Question about queued downloads from Amazon S3

[Dan Korneff]

@d-healey like this?


[d.healey]

@Dan-Korneff Scroll up - https://forum.hise.audio/topic/4635/question-about-queued-downloads-from-amazon-s3/12?_=1698944591828

[Dan Korneff]

@d-healey Redirect Only or X-Accel?

[d.healey]

@Dan-Korneff Redirect Only

[Dan Korneff]

@d-healey Are you using WooCommerce Amazon S3 Storage plugin to load your files?

https://woo.com/products/amazon-s3-storage/

[d.healey]

@Dan-Korneff Yup

[Dan Korneff]

@d-healey what about the redirect method for the S3 plugin?

[d.healey]

@Dan-Korneff I have that enabled

[Dan Korneff]

@d-healey I cannot get S3 hosted redirected downloads to initiate from HISE.
When I have all of the download methods set to Redirect, my server log looks like this when I download from the account section of my website (which successfully downloads):

"GET /?download_file=122&order=wc_order_dfsfsdfsdfasdf&email=myemail%40gmail.com&key=48c61d03-8e34-45ba-b54a-03b815444c5b HTTP/1.1" 302 5 "https://www.myserver.xyz/my-account/downloads/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/118.0.0.0 Safari/537.36 Edg/118.0.2088.69"

When I initiate the download from HISE, the webserver log says:

"GET /?download_file=122&order=wc_order_dfsfsdfsdfasdf&email=myemail%2540gmail.com&key=48c61d03-8e34-45ba-b54a-03b815444c5b HTTP/1.1" 302 5 "-" "juce"

The Referer header is set to "-" for some reason, but I don't think that is the culprit.

I've added the security measures suggested here:
https://woo.com/document/digital-downloadable-product-handling/#nginx-setting

Are there any other server configuration settings you can think of that would affect this?

[d.healey]

@Dan-Korneff I'm using a LiteSpeed server (same config as Apache), I've never used nginx so I can't offer much advice there sorry.

[Dan Korneff]

@d-healey hmm.... ok. I'm gonna boot up a LAMP stack and see how it behaves. That should let me know if it's an Nginx/Apache thing.

[Dan Korneff]

@d-healey OK! It does appear to be something that's different with Nginx redirect headers.
Just loaded up a site with Apache and the redirects work as expected.