<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=548485) </details> <!--IssueSummary end--> We are facing an issue where we cannot run our server software during development in gitlab-workspaces, since it will try to self-check and fail because it is missing the authentication cookie for the workspace. From what I can tell, the authentication cookie is [not optional and always required][1]. Is there any intended way that I am missing to reach endpoints exposed through the gitlab-workspaces-proxy from other clients than the developers browser? I currently see no "good" way other than supressing that self-check, since there is neither a way to get a valid authentication token inside the workspace nor a way to supply it to the server check. We are trying to run [remix with live reload][2], which will [reach out to itself][3] through the same url that it passes to clients to connect back to (the [endpoint specified in the devfile][4], like `https://3001-workspace-xxx-yy-zzzzzz.workspaces.cluster.example`). Since the request is done by the server, there is no authentication header set (unlike for the requests originating from the browser/development client) and it will get [redirected to the login page][1], failing the selfcheck and aborting the server start with an error. [1]: https://gitlab.com/gitlab-org/workspaces/gitlab-workspaces-proxy/-/blob/0.13/pkg/auth/middleware.go?ref_type=tags#L58 [2]: https://remix.run/docs/en/main/components/live-reload#origin [3]: https://github.com/remix-run/remix/blob/v2.11.1/packages/remix-server-runtime/dev.ts#L9 [4]: https://devfile.io/docs/2.2.0/devfile-schema#components-container-endpoints