Yes, the problem was because of the https definition of the server:
nginx.conf {
...
server {
listen 443 ssl http2 default_server;
...
}
...
}
So when studio is doing a call to the service endpoints it uses https schema and the async endpoint, e.g. https://localhost:5000/formrecognizer/documentModels/prebuilt-layout:analyze
The async endpoint of formrecognizer, custom-template etc. are returning an header with the paramter "Operation-Location", which cointains the url to check the result status. The issue was that the url in the Operation-Location header was http instead of https, e.g.
http://localhost:5000/formrecognizer/documentModels/prebuilt-layout/analyzeResults/id123456/
The UI tries then to get the result with the wrong shema and the error occures.
To resolve the issue I added a mapper and changed the returned header of the upstream server:
nginx.conf {
...
map $upstream_http_operation_location $operation_location {
"~^http://(.*)$" "https://$1";
}
server {
listen 443 ssl http2 default_server;
...
location /formrecognizer/documentModels/prebuilt-layout {
...
add_header 'Operation-Location' $operation_location always;
}
}
...
}
So in case there is a response header from upstream server with http it will map the schema to https.
You should also check the network traffic in develop mode, because the UI waits until the result is successfully and saves the result afterwards, i.e. if you don't wait for the result and close the browser, nothing will be saved and you have to run it again.