[Solved] S3 CloudFront Chrome Cors Error Css3d Request Twice Hotspot

tidytrax

Anfänger

Beiträge: 16

Wohnort: Brazil - Rio de Janeiro

Beruf: (IT Analyss

1

Freitag, 15. März 2019, 20:07

Hi, I got a problem, only in chrome and safari,
Firefox and Edge works fine and the problem happens only with hotspot Css3d,
And only some times with random hotspots, can be 2 or 20.

As i could saw the hotspot is request twice, once response 200 and in the second get failed and the below error appear in console.

Access to image at '7276d7a055036dc.png' from origin '' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.

I could fix using webgl, but gif and other stuff lost animation.
or
ignoring cache with 7276d7a055036dc.png?v=TIMESTAMP(random).

And why request twice? looks like the problem, if i use webgl, request once.

Dieser Beitrag wurde bereits 4 mal editiert, zuletzt von »tidytrax« (9. März 2021, 06:06)

Zum Seitenanfang

Douglas Rhiner

Fortgeschrittener

Beiträge: 141

Wohnort: San Anselmo, CA

Beruf: Code-Slave

2

Mittwoch, 20. März 2019, 18:03

Adding a random query string to your image must be done at the very last moment.

Zum Seitenanfang

klaus.krpano

Administrator

Beiträge: 13 499

3

Mittwoch, 27. März 2019, 12:29

Hi,

the two requests are because one request is by krpano with CORS-headers to the get the image size (and optionally also the pixels for the WebGL rendering, if that image would be rendered by WebGL) and the second request would be by the browser itself when the image would get rendered by CSS3D. But the browser doesn't send CORS-headers for this case.

That means two requests because once with CORS-headers and once without CORS-headers (only when rendering with CSS3D).

But even due the two requests the browser normally should load the second request from the cache. Only older Safari version were known to be buggy here...

So I would need some help to be able to reproduce that problem:
- Do you have a link to an example where this problem happens?
- What krpano version are you using?
- What Chrome version are you using?

Best regards,
Klaus

Zum Seitenanfang

tidytrax

Anfänger

Beiträge: 16

Wohnort: Brazil - Rio de Janeiro

Beruf: (IT Analyss

4

Dienstag, 9. April 2019, 20:25

Zitat von »klaus.krpano«

Hi,

the two requests are because one request is by krpano with CORS-headers to the get the image size (and optionally also the pixels for the WebGL rendering, if that image would be rendered by WebGL) and the second request would be by the browser itself when the image would get rendered by CSS3D. But the browser doesn't send CORS-headers for this case.

That means two requests because once with CORS-headers and once without CORS-headers (only when rendering with CSS3D).

But even due the two requests the browser normally should load the second request from the cache. Only older Safari version were known to be buggy here...

So I would need some help to be able to reproduce that problem:
- Do you have a link to an example where this problem happens?
- What krpano version are you using?
- What Chrome version are you using?

Best regards,
Klaus

Hi Klaus, I'm Usign KRpano 119pr16 Chrome Versão 73.0.3683.86.

For now I don't have a online link, but I will do soon and send.

Dieser Beitrag wurde bereits 1 mal editiert, zuletzt von »tidytrax« (9. April 2019, 20:43)

Zum Seitenanfang

Douglas Rhiner

Fortgeschrittener

Beiträge: 141

Wohnort: San Anselmo, CA

Beruf: Code-Slave

5

Montag, 13. Mai 2019, 21:38

tidytrax,

We had the same issue when we switched to AWS. Once we added the random string i.e. 12345.jpg?nocache=93186409346jhdfbw the issue was resolved. At least a workaround for now.

Zum Seitenanfang

tidytrax

Anfänger

Beiträge: 16

Wohnort: Brazil - Rio de Janeiro

Beruf: (IT Analyss

6

Dienstag, 9. Februar 2021, 09:10

Zitat von »klaus.krpano«

Hi,

the two requests are because one request is by krpano with CORS-headers to the get the image size (and optionally also the pixels for the WebGL rendering, if that image would be rendered by WebGL) and the second request would be by the browser itself when the image would get rendered by CSS3D. But the browser doesn't send CORS-headers for this case.

That means two requests because once with CORS-headers and once without CORS-headers (only when rendering with CSS3D).

But even due the two requests the browser normally should load the second request from the cache. Only older Safari version were known to be buggy here...

So I would need some help to be able to reproduce that problem:
- Do you have a link to an example where this problem happens?
- What krpano version are you using?
- What Chrome version are you using?

Best regards,
Klaus

Some news on this ? I still got this problem on 1.20.9
and almost 2 years without caching hotspot, low performance to load the hs.

Zum Seitenanfang

tidytrax

Anfänger

Beiträge: 16

Wohnort: Brazil - Rio de Janeiro

Beruf: (IT Analyss

7

Dienstag, 9. Februar 2021, 09:18

I have also tested on edge only works on firefox
Chrome, edge, firefox last version.

this is costing me too much because i can use cache on hotspot.

the error stop here e.loader.src=b

off"!=rc&&(e.loader.crossOrigin=rc),e.loader.src=b):(e.loading=!1,ta.reportError(1,e.getfullpath()+" loading error: "+b)))}}}