Skip to content

public/external route bound to new catalog #5604

@rshewitt

Description

@rshewitt

there's an nginx reverse proxy in front of new catalog which means new catalog shouldn't accept traffic directly. it can if either the public or external route is bound to it. only the internal route should be bound to it. all traffic should be handled by the proxy.

How to reproduce

  • run cf env datagov-catalog on prod

Expected behavior

  • only the internal route is mapped

Actual behavior

  • internal and public route is mapped.

Sketch

  • ensure only the internal route is mapped to datagov-catalog after deployment in all environments

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSoftware defect or bug

    Type

    No type

    Projects

    Status

    No status

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions