<p>What can be the reason for not being able to curl/use a rest API with some slugs i.e example.com/application/v2/xxxx.The docker image i use is the app from 
<a href="http://vespa.ai/" rel="nofollow noreferrer">http://vespa.ai/</a>
<a href="https://github.com/vespa-engine/docker-image/blob/master/Dockerfile" rel="nofollow noreferrer">https://github.com/vespa-engine/docker-image/blob/master/Dockerfile</a> </p>

<p>I have set up nodeport correctly and an ingress</p>

<p>i have tried various, for example default backend on the host:</p>

<pre><code>- host: example.com
http:
  paths:
  - backend:
      serviceName: myservice
      servicePort: 19071
</code></pre>

<p>or explicit using wildcard routing:</p>

<pre><code> - host: example.com
http:
  paths:
  - path: /*
    backend:
      serviceName: myservice
      servicePort: 19071
</code></pre>

<p>The strange thing is that doing curl externally (outside cluster):
curl -s --head <a href="http://example.com/ApplicationStatus" rel="nofollow noreferrer">http://example.com/ApplicationStatus</a>
Does return statusCode 200 OK</p>

<p>Doing
curl -s --head <a href="http://example.com/application/v2/tenant/" rel="nofollow noreferrer">http://example.com/application/v2/tenant/</a>
Return BAD_REQUEST from the application.</p>

<p>"error-code": "BAD_REQUEST",
"message": "<a href="http://example.com/application/v2/tenant/" rel="nofollow noreferrer">http://example.com/application/v2/tenant/</a>"</p>

<p>exec into the container and doing
curl -s --head <a href="http://localhost:19071/application/v2/tenant/" rel="nofollow noreferrer">http://localhost:19071/application/v2/tenant/</a>
works..</p>

<p>So either the application somehow match on hostname which is not correct when coming from the ingress or there is some other issues with the full uri not being proxied. </p>

<p>The source code for that app it too big to understand for me at the moment but looking in the source
<a href="https://github.com/vespa-engine/vespa/blob/f76406b88df47f6bdbf9d24feda4c9ff55c63e06/orchestrator/src/main/java/com/yahoo/vespa/orchestrator/resources/HostSuspensionResource.java" rel="nofollow noreferrer">https://github.com/vespa-engine/vespa/blob/f76406b88df47f6bdbf9d24feda4c9ff55c63e06/orchestrator/src/main/java/com/yahoo/vespa/orchestrator/resources/HostSuspensionResource.java</a>
It might explain why it returns the error message.</p>

<p>Everything else seems to work, configserver and application.</p>

<p>Is it the app itself or kubernetes that might be the problem here ? </p>

<p>HostSuspensionResource should not be involved here I think. The restapi entry point is the ApplicationHandler class for the call you are making.</p>

<p>What happens when you curl inside the container with the default port (i.e not the 'internal' 19071 port)?</p>
