[Keith Lee]

I think I have messed around Nginx’s add_header. I have removed recent changes in my Nginx configuration, and all new images are displayed properly. Old images, including the one you sampled, are not, which means those images have the earlier header.

I just need to find a way to purge all earlier headers.

Thanks for the help. You can close the ticket.

[Keith Lee]

I’ve also checked that part as well. I did guess that it could be CORS error, but it’s not like I have implemented any cross-domain security measure. I’ve tried with a number of suggested options via googling, but nothing works so far.

– https://stackoverflow.com/questions/56057136/fixing-the-access-control-allow-origin-header-contains-multiple-values-error-i
– https://github.com/caprover/caprover/issues/245

Above options tell me that I am supposed to add header for the origin, but that I thought it may further disable Super RSS’s functionality. Can you please double check that it is not the problem of feed? If it is just the matter of blocking images being pulled to other websites, guess I can at least narrow down the cause thus the potential solutions.

[Keith Lee]

Thx for the update. I’ve managed to find a way to create proper image feed for image categories. Problem solved.

[Author]

Posts