Did you remove services.ports.http_options.response.headers feature?

1

We’ve been using this TOML config code for a few months but it appears to have suddenly stop working today causing a CORS error in our production. Any idea why this could be?

Original code that our config was based on Edge headers.

  # https://community.fly.io/t/edge-headers/9278
  [services.ports.http_options.response.headers]
    Access-Control-Allow-Origin = "*"
    Access-Control-Allow-Methods = "*"
    Access-Control-Allow-Headers = "*"

This is what curl is giving us back, notice the missing headers:

< HTTP/2 401
< content-type: application/json; charset=utf-8
< content-length: 39
< date: Mon, 06 Feb 2023 21:26:17 GMT
< server: Fly/8bd41836 (2023-02-03)
< via: 2 fly.io
< fly-request-id: 01GRM9YP96RPANDJGHMQZQDPB0-yyz
<
2

A redeploy of the app brought back the headers being sent by edge. :confused:

3

Did you use updated flyctl each time? We yanked a flyctl release this morning that was eating parts of the fly.toml it shouldn’t have been.

4

Yeah each time, must have been that!

1 Like