OpenGis exception?

Since yesterday evening, I have on both my 3 browsers (Safari, Firefox, Chrome) this same exception when I access to
I remember having read a similar question asked last year but I don’t remember in which category, nor what is the work-around. Any idea?
{“config”:{“transformRequest”:{},“transformResponse”:{},“timeout”:0,“xsrfCookieName”:“XSRF-TOKEN”,“xsrfHeaderName”:“X-XSRF-TOKEN”,“maxContentLength”:-1,“headers”:{“Accept”:“application/json, text/plain, /”},“method”:“get”,“responseType”:“text”,“url”:“"},“request”:{},“response”:{“data”:"<?xml version='1.0' encoding=\"UTF-8\"?>\n<ServiceExceptionReport version=“1.3.0”\n\txmlns=“"\n\txmlns:xsi=“”\n\txsi:schemaLocation="”>\n\t\n\t\t\n\t\n”,“status”:400,“statusText”:"",“headers”:{“content-type”:“application/xml”},“config”:{“transformRequest”:{},“transformResponse”:{},“timeout”:0,“xsrfCookieName”:"XSRF-


Thanks for the report. Something went wrong when we were updating things. Unfortunately I don’t know the workaround. But we are already preparing a fix for this.

Thank you very much. I’ll try again from time to time.
And you may want to post an update on the forum when the fix is installed and running.

The problem should now be resolved.

Hello Ziga,
Thank you for the trial, but as far as it goes on my side, the result is not conclusive.

  • I still have an error message in Safari.
  • In Firefox the page keeps looping on “Loading”.
  • In Chrome the page loops and ultimately shows the map layer but no satellite data whatever the date I choose and at 100% nebulosity
    I’m copying and pasting the Safari error message just now FYI, then I’ll compare it with the previous error message of last week:

{“config”:{“transformRequest”:{},“transformResponse”:{},“timeout”:0,“xsrfCookieName”:“XSRF-TOKEN”,“xsrfHeaderName”:“X-XSRF-TOKEN”,“maxContentLength”:-1,“headers”:{“Accept”:“application/json, text/plain, /”},“method”:“get”,“responseType”:“text”,“url”:“"},“request”:{},“response”:{“data”:"<?xml version='1.0' encoding=\"UTF-8\"?>\n<ServiceExceptionReport version=“1.3.0”\n\txmlns=“"\n\txmlns:xsi=“”\n\txsi:schemaLocation="”>\n\t\n\t\t\n\t\n”,“status”:400,“statusText”:"",“headers”:{“content-length”:“418”,“content-type”:“application/xml”},“config”:{“transformRequest”:{},“transformResponse”:{},“timeout”:0,“xsrfCookieName”:“XSRF-TOKEN”,“xsrfHeaderName”:“X-XSRF-TOKEN”,“maxContentLength”:-1,“headers”:{“Accept”:“application/json, text/plain, /”},“method”:“get”,“responseType”:“text”,“url”:“"},“request”:{}},“line”:1,“column”:660975,“sourceURL”:"”}

Hello Ziga,
It’s back to normal again.
Thanks a million.


1 Like

Good to know, Henry.
Thank you very much.

The situation is now back to normal.
The error message appeared Firefox indeed, but also using Safari and Chrome. Now Ziga repaired the bug and things are fine again. But your tip is good to know.

1 Like