Unfortunately, that's not the case for me. On the server side everything is o.k.
Your colleague has indeed already looked over it, only discovered no error. It's sad after I even made the logs available to him.
I'm not the only one struggling with the problem.
The bottom line is that a url within the PB is not properly resolved.
The Dev tool also shows this because there is a session mismatched
JSON
{
"success": true,
"message": null,
"messages": null,
"data": {
"message": "Session mismatched."
}
}
raw data
{
"success": true,
"message": null,
"messages": null,
"data": {
"message": "Session mismatched."
}
}
headers
X-Firefox-Spdy: h2
content-type: application/json
date: Tue, 08 Aug 2023 15:07:50 GMT
server: Apache
x-content-type-options: nosniff
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,/;q=0.8
Accept-Encoding: gzip, deflate, br
Accept-Language: de,en-US;q=0.7,en;q=0.3
Connection: keep-alive
DNT: 1
Host: test.kaole.de
Sec-Fetch-Dest: document
Sec-Fetch-Mode: navigate
Sec-Fetch-Site: none
Sec-Fetch-User: ?1
TE: trailers
Upgrade-Insecure-Requests: 1
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/116.0