Hi David,

Do you connect to SSL via a proxy? This usually happens when the proxy (usually IIS) isn't properly configured to pass the parameters of the request. This can usually be accomplished by tweaking a bit the parameters of the proxy configuration. You can usually check whether this is the case by temporarily disabling the proxy or accessing the artifacts' url without using the proxy, which is exactly what you described. Can you check that?

Hi Denis,

Thanks for your reply. Yes, we do use IIS as a reverse proxy. I have tried bypassing it and it works as you suggested. I will take a look at the re-write rules.

I have managed to resolve the problem. It took me a lot longer that it should so I thought I would share what I did to resolve it.

The main issue I faced was with double encoding of URLs. TeamCity outputs an encoded URL for me to click in the UI, however, the existing IIS rewrite rule was then encoding this again resulting in the TeamCity Apache server not being unable to resolve the artefact.

To fix the problem, ensure you have version 2.1 or higher of the IIS rewrite module installed. Turn useOriginalURLEncoding to false (see https://serverfault.com/a/882301 for instructions). If you do not set the usrOriginalURLEncoding option then you have an older version of the rewrite module.

Modify your rewrite rule to the following:

<rule name="TeamCityReverseProxy" stopProcessing="true">
  <match url="(.*)" />
  <conditions>
    <add input="{UNENCODED_URL}" pattern="/(.*)" />
  </conditions>
  <action type="Rewrite" url="http://localhost:8080/{C:1}" />
</rule>

Setting useOriginalURLEncoding to false was the key to fixing the issue. It is defaulted to true which was causing the double encoding. You can read more about it in the Preserve original URL encoding section in this blog: https://blogs.iis.net/iisteam/url-rewrite-v2-1

Having been running this fix for a while now, we identified another problem where we were unable to delete parameters due to this rewrite rule. We kept getting an error message saying 'Unknown action removeParameter,removeParameter'. To fix the problem we had to modify the rewrite rules to be the following:

<rules useOriginalURLEncoding="false">
  <clear />
  <rule name="TeamCityDefaultReverseProxy" enabled="true" stopProcessing="true">
    <match url="(.*)" />
    <conditions logicalGrouping="MatchAll" trackAllCaptures="false">
      <add input="{UNENCODED_URL}" pattern="(.*%2B.*)" negate="true" />
      <add input="{URL}" pattern="/(.*)" />
    </conditions>
    <action type="Rewrite" url="http://localhost:8080/{C:1}" logRewrittenUrl="false" />
  </rule>
  <rule name="Handle artifacts with + in path - TeamCity reverse proxy" stopProcessing="true">
    <match url="(.*)" />
    <conditions>
      <add input="{UNENCODED_URL}" pattern="/(.*)" />
    </conditions>
    <action type="Rewrite" url="http://localhost:8080/{C:1}" />
  </rule>
 </rules>

The first rule processes all of the requests, except for those that contain a '+' (%2B). They fall to the second rule which builds the rewrite rule using the unencoded url.