Read OCR container doesn't work correctly when using "vision" in the hostname

Hi Jeroen,

Thank you for reaching out on the Microsoft Q&A.
The root cause of the issue you’re seeing with the Read OCR container is not a bug in the OCR logic itself, but how the container constructs and returns the Operation-Location URL when the hostname contains the substring vision.

The Read container tries to build the callback URL from the incoming request’s host, but if the host name includes the string “vision”, the internal URL parser incorrectly strips out parts of the host and port, which breaks the returned URL. That’s why calling:

http://azure-vision:5000/vision/v3.2/read/analyze

returns an Operation-Location like:

http://azure-vision/v3.2/read/analyzeResults/…

…with both the port and the “vision” segment removed which leads to failed polling of results.

What’s happening:

The container expects to reconstruct the full callback URL.

When the host includes “vision”, the parser incorrectly drops parts of it.

• This affects any host like azure-vision, visionxyz, or hostnames with .azure-vision. in them.

Please follow the below steps for fixing the issue:
Rename the hostname so that it does not include the substring vision. For example:

Instead of azure-vision:5000, use azureocr:5000

Instead of read-svc.azure-vision.svc.cluster.local, use read-svc.azureocr.svc.cluster.local

Once the host doesn’t contain the literal vision string, the container will return the correct Operation-Location including the port and full path and the Read API calls will work as expected.

I hope this has been helpful! Please let me know if there are any remaining questions or additional details, I can help with, I’ll be glad to provide further clarification or guidance.

Thankyou!