Next links get redirected, breaking CORS about medserve HOT 4 CLOSED

Original comment by Dion McMurtrie (Bitbucket: dion_mcmurtrie, GitHub: Unknown)

Jetty seemed to be the culprit here redirecting for a WAR deployed at /fhir - changed to a root deployment with a web context of /fhir and it works without redirect. This added an nginx webserver in front for the static content - probably not a bad thing anyway.

from medserve.

Original comment by Dion McMurtrie (Bitbucket: dion_mcmurtrie, GitHub: Unknown)

Sorry @j0hngr1mes I didn't do a docker-compose pull so I had the old medserve image. It is fixed now.

from medserve.

Original comment by John Grimes (Bitbucket: j0hngr1mes, GitHub: Unknown)

@dion_mcmurtrie Are you sure you actually deployed the changes we made to fix this ticket?

Code seems fixed, the latest image on Docker image seems fixed - but medserve.online still exhibits the redirect behaviour.

from medserve.

Original comment by John Grimes (Bitbucket: j0hngr1mes, GitHub: Unknown)

This might not have to do with the actual CORS configuration, it may have to do with the web server configuration specifically in place for medserve.online.

On my local environment, with a bare Medserve container, I don't have this problem. In fact, I don't get a redirect at all when following a next link, I get a 200 OK.

I think what is happening on medserve.online is that the following sort of request:

http://medserve.online/fhir?_getpages=bb67a41b-42c6-4811-bdea-5c32bbb48d61&_getpagesoffset=100&_count=100&_bundletype=searchset

Gets redirected to:

http://medserve.online/fhir/?_getpages=bb67a41b-42c6-4811-bdea-5c32bbb48d61&_getpagesoffset=100&_count=100&_bundletype=searchset

Note the slash after fhir. The redirect is not CORS-aware.

Not sure what you have in front of the Medserve container on medserve.online, but we need to re-configure it to suppress this behaviour.

from medserve.