URL problem on local staging

Resolved Nazrinn
(@nazrinn)

5 years, 1 month ago

Hi there. So I use dummy images for my blog posts. They display correctly in the backend and page builder. However in the frontend, the image URL is broken because some extra slashes + no protocol tags got in there before the domain name.

Backend url:
https://ml275xldtxd5.i.optimole.com/60b8Baw.1PqT~2620e/w:auto/h:auto/q:75/process:6419/id:ccc7e149e565fdbc2c5172df2aaee995/http://localhost/b78fe279-8db6-3a56-ae15-ce10745e11f7.jpg

Frontend url:
https://ml275xldtxd5.i.optimole.com/60b8Baw.1PqT~2620e/w:300/h:200/q:75/id:3552ec49f1eb4c8a6c72514fa257ddc0///localhost:3000/2cdf2f26-b052-39ab-a782-4c1374da1d30.jpg

Any reason why that might be the case?

Viewing 6 replies - 1 through 6 (of 6 total)

Plugin Support Vytis
(@bvytis)

5 years ago

Hi @nazrinn,

Our developers identified the reason for this issue with extra slashes and working on the fix. We will update this thread once a fix is released.

Thank you for your patience.

Thread Starter Nazrinn
(@nazrinn)

5 years ago

Wow! Thank you Vitys.

Looking forward to the next update.

(Hope you noticed a port number was added to the URL too.)

Plugin Support Vytis
(@bvytis)

5 years ago

Hi @nazrinn,

The problem with the missing schema is fixed now. For example, https://ml275xldtxd5.i.optimole.com/60b8Baw.1PqT~2620e/w:300/h:200/q:75/id:3552ec49f1eb4c8a6c72514fa257ddc0///localhost/2cdf2f26-b052-39ab-a782-4c1374da1d30.jpg is working.

However, the https://ml275xldtxd5.i.optimole.com/60b8Baw.1PqT~2620e/w:300/h:200/q:75/id:3552ec49f1eb4c8a6c72514fa257ddc0///localhost:3000/2cdf2f26-b052-39ab-a782-4c1374da1d30.jpg will not work because the domain is stored like localhost not localhost:3000.

URLs will work with a missing schema like in the provided example but not with the :3000` port unless this how they were stored initially. (ie. you stored the hash for localhost not localhost:3000 so it is expected not to work this way)

Thread Starter Nazrinn
(@nazrinn)

5 years ago

I see. Thank you Vytis!

Do you know if maybe the port could be simply ignored?

Also, is there any particular reason why the hashes uses the URL instead of a generic ID? I feel like it caused me a lot more problem than it helped.

The website has a huge amount of photos so the CDN helps significantly in reducing backup errors and transfer time. Keeping a single “domain” would also help me reduce the amount of duplicated photos that is already in my account. What is your philosophy on that?

Plugin Support Vytis
(@bvytis)

5 years ago

Hi,

Apologies for the delay on this thread and yes this issue will be fixed.
Ports are being ignored, however, in your case, it was related to that slashes /// issue and it’s also the reason the URL was not working properly with a port, our developers will address this.
Thread Starter Nazrinn
(@nazrinn)

5 years ago
Looking forward to it! I trust your team will get through it. Otherwise I am very satisfied with Optimole’s performances. =)

Thank you Vitys!

Also regarding your philosophy, is that something you are in the position to answer?
- This reply was modified 5 years ago by Nazrinn.

Viewing 6 replies - 1 through 6 (of 6 total)

The topic ‘URL problem on local staging’ is closed to new replies.