-
Bug
-
Resolution: Obsolete
-
Major
-
None
-
None
-
None
-
None
-
-
Empty show more show less
-
HL & LD 17, HL & LD 18, HL & LD 19, HL & LD 20
-
3
A delivery endpoint which is able to successfully return a response to a browser when there is no error in the request - should also successfully return an error response when a problem occurs. Currently, it does not. For some reason when the delivery endpoint returns an error message - such as in the case of a 404 or 500 - the browser shows a CORS error and does not return the error response as expected.
Details
When calling delivery rest endpoints and response is e.g.
"error":
or not authorized, or some 500 in rest call Magnolia returns CORS error.
It creates HUGE confusion in finding the real cause of error.
In couple cases blocked POC prospects for days as they did not knew what else to do.
CORS is correctly added naturally
Timeboxed for investigation: 3 SP
- is cloned by
-
PAGES-483 SPA cannot reach template endpoints by default
- Closed
- is related to
-
MAGNOLIA-7969 CORS headers not added for unauthorized (401) requests
- Closed
-
MGNLSITE-103 CORS headers not added for unauthorized (401) requests
- Closed
- is superseded by
-
MAGNOLIA-7969 CORS headers not added for unauthorized (401) requests
- Closed
-
MGNLSITE-103 CORS headers not added for unauthorized (401) requests
- Closed