Skip to content

Service connect namespace BAN verb reserved

0

I have an ECS Fargate cluster with two services (Varnish and an app) using Service Connect with the namespace test.local. When I run curl -X BAN http://varnish.test.local:port from the app container (app.test.local), I get a "Bad Request" error. The same error occurs even when no Varnish containers are running. Is BAN a reserved verb in AWS Service Connect or the Application Load Balancer? I have a workaround using POST, but I'd like to understand what's happening.

2 Answers
0

BAN is not a reserved word/verb in AWS. However, ALB officially supports: GET, HEAD, POST, PUT, PATCH, DELETE, OPTIONS, CONNECT, TRACE. It does not support BAN. ALB rejects methods it cannot parse as part of its HTTP/1.1 validation layer. If the method token does not meet its RFC expectations or conflicts with internal rules, ALB returns 400 or 50* status codes.

EXPERT

answered 9 months ago

  • Thanks for your reply, one question still remains I also use the word/verb PURGE which is not in the officially supported list but that works fine. That is why I think it was a reserved verb, technically I don't know if Service Connect uses ALB or another service that uses BAN as a reserved word/verb for its own usage.

0

Hey,

Hope you're keeping well.

BAN isn’t reserved by AWS Service Connect, but it’s not part of the HTTP methods supported by an Application Load Balancer. ALB only accepts standard verbs like GET, POST, PUT, etc., and will return 400 Bad Request if it sees an unrecognized method before passing traffic to your target. Since Service Connect traffic between ECS services still flows through an ALB listener when using an internet/NLB-to-ALB path, unsupported methods are dropped at that layer.

Thanks and regards,
Taz

answered 9 months ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.