Skip to content
This repository has been archived by the owner on Jan 30, 2024. It is now read-only.

Incorrect proxy destination for publicapi #6059

Closed
rubenarakelyan opened this issue Jul 2, 2017 · 4 comments
Closed

Incorrect proxy destination for publicapi #6059

rubenarakelyan opened this issue Jul 2, 2017 · 4 comments

Comments

@rubenarakelyan
Copy link
Contributor

rubenarakelyan commented Jul 2, 2017

The default proxy destination of publicapi (as defined in https://github.com/alphagov/govuk-puppet/blob/master/modules/govuk/manifests/apps/publicapi.pp#L38) is three subdomains that represent three different apps (whitehall, content-store and rummager). This is incorrect since an array of destinations denotes round-robin load balancing which doesn't make sense if you're balancing between different apps.

The more specific location blocks in the config actually take care of all traffic routing so this error doesn't cause any issues, but since it also doesn't get any traffic it should probably be removed altogether.

@MatMoore
Copy link
Contributor

MatMoore commented May 4, 2018

Did we ever fix this?

@rubenarakelyan
Copy link
Contributor Author

Nope, AFAIK it's still like that. I think we should remove the round-robin stuff and just have location blocks for the various apps but it needs to be tested to make sure we don't break the public API.

@MatMoore
Copy link
Contributor

MatMoore commented May 4, 2018

Yep. Could maybe do it as a firebreak task if it doesn't fit on the platform health backlog.

@tijmenb
Copy link
Contributor

tijmenb commented Aug 15, 2019

All of the routing is now done via the publishing-api/router and publicapi has been retired (#8637). Closing!

@tijmenb tijmenb closed this as completed Aug 15, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants