CORS issue with photos being displayed from /uploads URL when referencing localhost

[mitpjones]

Hi,

I am having trouble tracking down where the URL (/uploads) for displaying the photos is constructed.

1. If I were to use the following URL https://102.98.39.120/gallery, the photos are correctly retrieved by a GET requests similar to the following:

https://102.98.39.120/uploads/small2x/36/7c/3a1c4676928e44c4925d43aab98c.jpg

2. However, if I were to use the following URL https://localhost/gallery, the photos are incorrectly retrieved via GET requests to the same URL, where as they should be using the 'base href' 'localhost' i.e.

https://localhost/uploads/small2x/36/7c/3a1c4676928e44c4925d43aab98c.jpg

In the second case this results in a CORS issue and the photos are not displayed. The other URLs e.g. /api and /build/assets correctly use 'localhost' e.g.

https://localhost/build/assets/dijkstrajs-C00ieaqj.js and https://localhost/api/v2/Auth::user

I am wondering if the /api and /build/assets URL are constructed on the client using 'base href' where as the /uploads URL are constructed on the server? If this is so then it could be my bad forwarding on the incorrect PATH information from my proxy server but I would like to find the place where the URLs are constructed to interrogate what is actually used.

Thanks,

Tim

[ildyria]

It really depends how you set up your APP_URL, when going via the localhost, what happens when you check the diagnostics?

And yes you are correct, we are constructing the urls for images on server side, this is done via with the value provided in the environment variable mentioned above.