Apollo Router endpoint to handle both /graphql and /graphql/ requests

[ernestaskardzys]

Is your feature request related to a problem? Please describe.

Currently we have the following following URL that serves as Apollo Router endpoint: https://www.example.net/graphql

However, there are some legacy (!) clients that use "old" endpoint: https://www.example.net/graphql/ (note "/" at the end). Unfortunately, due to backwards compatibility reasons we need to support both endpoints.

Based on https://www.apollographql.com/docs/router/configuration/overview/#endpoint-path , Apollo Router does not support any additional symbols at the end of path, which ends with /graphql

Therefore, we need a way to support both endpoints: /graphql and /graphql/

Describe the solution you'd like

I would prefer for the Apollo Router to handle both types of requests - going to either https://www.example.net/graphql or https://www.example.net/graphql/

Describe alternatives you've considered

As we use GCP and Kubernetes, there might be a way to write a custom "Ingress" CRD which redirects requests to self - hosted Apollo Router instance.

Additional context

This feature request is due to backward - compatibility reasons.