You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Private S3 buckets requires HTTP basic authentication which is not something we'd support on our public service (see #341). If you're able to host your own solution, you can support this by doing something like this within the ngnix configuration:
location/s3/ {
weserv filter;
# The S3 bucket we useproxy_pass http://libvips-packaging.s3.amazonaws.com/;
proxy_set_header Host libvips-packaging.s3.amazonaws.com;
# Authorization should not be needed on public bucketsproxy_set_header Authorization '';
# Header configurationproxy_hide_header x-amz-id-2;
proxy_hide_header x-amz-request-id;
proxy_hide_header x-amz-meta-server-side-encryption;
proxy_hide_header x-amz-server-side-encryption;
proxy_hide_header Set-Cookie;
proxy_ignore_headers Set-Cookie;
# Intercept proxy errorsproxy_intercept_errors on;
# Enable the upstream persistent connectionproxy_http_version1.1;
proxy_set_header Connection '';
}
is it same as adding https://wsrv.nl/?url=s3 image url....? I am getting 404 this way
The text was updated successfully, but these errors were encountered: