When you're making a request with curl from the command line, you're making a direct request to the service. But when you try to access the service through a web browser, it's going through your Nginx reverse proxy, which may be introducing the issue.

As you mentioned that you are seeing a redirect to <http://10.235.77.22/index.css> in the browser, it sounds like there may be an issue with the handling of relative paths for static assets in your Airbyte web application when it's accessed through a subdirectory.

To confirm this, you can use your browser's developer tools to inspect the network requests being made when you access the page. In Chrome, for instance, you would open the developer tools by right-clicking anywhere on the page, select "Inspect", then select the "Network" tab. Refresh the page and look at the requests being made.

You're expecting to see requests to <http://10.235.77.22/airbyte/index.css>, but it sounds like you might instead be seeing requests to <http://10.235.77.22/index.css>. If that's the case, it suggests that the web application is not properly prefixing its asset paths with /airbyte/.

This might be a limitation in Airbyte's handling of being served from a subdirectory. Not all web applications support being served from a subdirectory out of the box, and it's possible that Airbyte is one of them.