Skip to content

Fix SWAPI GraphQL backend URL#70

Merged
obokaman-com merged 1 commit into
mainfrom
fix/swapi-graphql-backend-url
Jun 3, 2026
Merged

Fix SWAPI GraphQL backend URL#70
obokaman-com merged 1 commit into
mainfrom
fix/swapi-graphql-backend-url

Conversation

@obokaman-com

Copy link
Copy Markdown
Member

The SWAPI GraphQL backend behind /starwars_films/{movie_id} was pointing at /.netlify/functions/index, which now 301-redirects. KrakenD doesn't follow the redirect, so the endpoint was broken.

Switched the url_pattern to /graphql, which returns 200. Verified end-to-end through the gateway (/starwars_films/1 -> 200). Change applied to the Flexible Config template and the compiled krakend.json.

The /.netlify/functions/index path now 301-redirects, which breaks the
/starwars_films/{movie_id} endpoint since KrakenD doesn't follow the
redirect. The SWAPI GraphQL API is served at /graphql now. Updated the
Flexible Config template and the compiled krakend.json.
@obokaman-com obokaman-com merged commit 64b2f79 into main Jun 3, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants