Bug with Rest API Resource Headers between environments

  1. I added the Content-Type: application/json header to my Production Resource Configuration and saved.
  2. I switch to Staging to add it again. The value is already present; I just added the key again and saved it.
  3. I confirmed the header is NOT being included in Staging requests.
  4. I go back to my staging configuration and refresh the page to confirm the header looks good and it does.
  5. Header is still not being included.
  6. I delete that header and make a new (identical) one and save again.
  7. Now the header is included.

This tripped me up a few times this week, but now I make sure make a 2nd header and delete the first one that was prefilled.

Hi @henrymeiklejohn Thanks for flagging this bug! [Edit] I thought I was running into the same issue, but I haven't been able to reproduce this in our test environment. Would love to know if you're still running into this! A screen recording would be helpful for getting a fix in place

1 Like