![]() For example, TeamCity relies on the X-TC-CSRF-Token header added by the clients. Headers like Referer and Origin and all unknown headers should be passed to the TeamCity web application in the unmodified form. The proxy should be configured with the generic web security in mind. If you need to run the server under a different context, note that the context-changing proxy should conceal this fact from the TeamCity: for example, it should map server redirect URLs as well as cookies setting paths to the original (external) context. See also the TeamCity server context changing instructions. Note: An internal TeamCity server should work under the same context (that is part of the URL after the host name) as it is visible from outside by an external address. These URLs are used to generate absolute URLs in the client redirects and other responses.Īfter configuring the proxy, you will also need to change the Server URL value in TeamCity Global Settings to the proxy URL. Set up a reverse proxy as described below.Ĭonfigure the Tomcat server bundled with TeamCity. To make sure TeamCity "knows" the actual absolute URLs used by the client to access the resources, you need to: It is visible to the outside world as a public URL. Refer to your proxy server documentation for more details.Ĭonsider the example: TeamCity server is installed at a local URL. We strongly recommend that you configure HTTPS on the proxy level. Proxy on the TeamCity agent side for agent-to-server connections Reverse proxy installed in front of the TeamCity Server web UI ![]() This article gives general recommendations on configuring the following proxy types:
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |