Inconsistent/unexpected CF-Ray header format

General
1

What is the name of the domain?

n/a

What is the error number?

n/a

What is the error message?

n/a

What is the issue you’re encountering

I have noticed recent requests to my webserver through CF have a Ray-ID that is missing the 3 character DC string at the end. Is this expected?

What steps have you taken to resolve the issue?

None. I first noticed this issue a couple of months ago. It is now happening again regularly (within the past week), even though 2-4 weeks before that, it was not occurring. I can see it’s an issue from observing the string in my NGINX logs where I have configured NGINX to log the CF-Ray header value. Note I have only noticed this change because I have configured my NGINX instance to regex match the CF-Ray and, if an unexpected format is issued by CF, a 444 is returned, so to mitigate breaking my sites, I’ve adjusted the regex to account for this observed abnormality. My question is really if this is expected behaviour and if CF themselves know about it.

What are the steps to reproduce the issue?

Browsing to any of my websites through CF causes some requests to have a CF-Ray which is lacking the 3 character DC code. Some recent examples are below:

8c1a0bfe1ed19436
8c1a0bfedfe39436-LHR
8c1a0c0d1a219436
8c1a0c95ac569436
8c1a0cab39549436
8c1a101a4820c391-SEA
8c1a1749cc6ba916
8c1a18f5ad0f0a0d-IAD
8c1a19b1685676a8-SEA
8c1a1c64fc0aebaf-SEA
8c1a1d305ec51e22
8c1a1d31fca91e22
8c1a1d510e781e22

1 Like
2

Hey there!

Thank you for bringing this to our attention.

We’ve let Engineering know, and they are able to reproduce this behavior. They are looking into the root cause, and will get a fix out to address this issue when the investigation concludes.

4 Likes
3

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.