-
Notifications
You must be signed in to change notification settings - Fork 11.4k
Add FAQ: random hostnames in HTTP logs for partial zones #27398
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
+128
−13
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Explains why customers with partial (CNAME) zones may see unexpected hostnames in HTTP request logs due to Host header injection attacks. Includes identification patterns and WAF custom rule solution.
Contributor
|
This pull request requires reviews from CODEOWNERS as it changes files that match the following patterns:
|
Contributor
Explains why customers with partial (CNAME) zones may see unexpected hostnames in HTTP request logs due to Host header injection attacks. Includes identification patterns and WAF custom rule solution.
…flare/cloudflare-docs into rian/logs-random-hostnames
angelampcosta
approved these changes
Jan 5, 2026
|
في الاثنين، ٥ يناير ٢٠٢٦، ٤:٤٢ م Rian van der Merwe <
***@***.***> كتب:
… Merged #27398 <#27398>
into production.
—
Reply to this email directly, view it on GitHub
<#27398 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/B3RKUIH5YH2XD6FKHXVEYAD4FJZ35AVCNFSM6AAAAACQUXSC3SVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMRRHA2TKNRQGIZDQOI>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***
com>
|
|
في الاثنين، ٥ يناير ٢٠٢٦، ٤:٥٠ م اسماعيل سعيد عبدالعظيم <
***@***.***> كتب:
…
في الاثنين، ٥ يناير ٢٠٢٦، ٤:٤٢ م Rian van der Merwe <
***@***.***> كتب:
> Merged #27398 <#27398>
> into production.
>
> —
> Reply to this email directly, view it on GitHub
> <#27398 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/B3RKUIH5YH2XD6FKHXVEYAD4FJZ35AVCNFSM6AAAAACQUXSC3SVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMRRHA2TKNRQGIZDQOI>
> .
> You are receiving this because you are subscribed to this thread.Message
> ID: ***@***.***
> .com>
>
|
ravindra-dyte
pushed a commit
to dyte-io/cloudflare-docs
that referenced
this pull request
Jan 7, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Adds a new FAQ page explaining why customers with partial (CNAME) zones see unexpected hostnames in their HTTP request logs.
What this PR adds
New page:
/logs/faq/random-hostnames-partial-zones/Covers:
Updated: /logs/faq/index.mdx
Why
This is a common support question for customers using partial zone setups. The behavior is expected (Cloudflare logs the
Hostheader as-is) but can be confusing without context.