{{ message }}
Repository navigation
Fix inaccurate OPTIONS method example - #46220
Closed
Khogendrarupini wants to merge 3 commits into
Closed
Khogendrarupini wants to merge 3 commits into
Khogendrarupini wants to merge 3 commits into
Conversation
Khogendrarupini
requested review from
hamishwillee
and removed request for
a team
October 21, 2026 05:08
github-actions
Bot
added
Content:HTTP
Contributor
Khogendrarupini
commented
Oct 21, 2026
Khogendrarupini
left a comment
Khogendrarupini
left a comment
Contributor
Author
There was a problem hiding this comment.
Applied the suggested Markdown formatting change to address the linter feedback. No changes were made to the technical content...
… OPTIONS Description Updated the "Identifying allowed request methods" section of the HTTP OPTIONS method documentation to use https://httpbin.org instead of https://example.org. Updated the illustrative HTTP response to reflect the example provided in issue mdn#46204, showing an HTTP/2 200 response with an Allow: HEAD, OPTIONS, GET header. Clarified that response status codes and headers depend on the server's implementation and configuration. Also applied the suggested Markdown formatting change from the pull request review. Motivation The original example showed a 204 No Content response and an Allow header, but the documented curl command against https://example.org returns 405 Method Not Allowed without an Allow header, as reported in issue mdn#46204. This made the example inaccurate and potentially confusing for readers. Using https://httpbin.org aligns the example with the response reported in the issue and demonstrates how an OPTIONS request can return an Allow header listing supported request methods. Additional details Only the "Identifying allowed request methods" section in files/en-us/web/http/reference/methods/options/index.md was updated, along with the Markdown formatting adjustment requested during review. No unrelated documentation files were changed. Related issues and pull requests Fixes mdn#46204
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
| - [HTTP headers](/en-US/docs/Web/HTTP/Reference/Headers) | ||
| - {{HTTPHeader("Allow")}} header | ||
| - [CORS](/en-US/docs/Web/HTTP/Guides/CORS) | ||
| - |
Contributor
There was a problem hiding this comment.
[mdn-linter] reported by reviewdog 🐶
Suggested change
… OPTIONS Description Updated the "Identifying allowed request methods" section of the HTTP OPTIONS method documentation to use https://httpbin.org instead of https://example.org. Updated the illustrative HTTP response to reflect the example provided in issue mdn#46204, showing an HTTP/2 200 response with an Allow: HEAD, OPTIONS, GET header. Clarified that response status codes and headers depend on the server's implementation and configuration. Also applied the suggested Markdown formatting change from the pull request review. Motivation The original example showed a 204 No Content response and an Allow header, but the documented curl command against https://example.org returns 405 Method Not Allowed without an Allow header, as reported in issue mdn#46204. This made the example inaccurate and potentially confusing for readers. Using https://httpbin.org aligns the example with the response reported in the issue and demonstrates how an OPTIONS request can return an Allow header listing supported request methods. Additional details Only the "Identifying allowed request methods" section in files/en-us/web/http/reference/methods/options/index.md was updated, along with the Markdown formatting adjustment requested during review. No unrelated documentation files were changed. Related issues and pull requests Fixes mdn#46204
BHUVANSH855
reviewed
Oct 21, 2026
BHUVANSH855
left a comment
BHUVANSH855
left a comment
Contributor
There was a problem hiding this comment.
I think this is duplicate of #46206.
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
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.
Description
Updated the "Identifying allowed request methods" section in the HTTP OPTIONS method documentation to use https://httpbin.org instead of https://example.org. Updated the illustrative HTTP response and clarified that response status codes and headers depend on the server's implementation and configuration.
Motivation
The previous example showed a 204 No Content response and an Allow header that could not be reproduced using the documented curl command against https://example.org. This change uses an alternative endpoint to make the example clearer and removes the outdated response details.
Additional details
Only the "Identifying allowed request methods" section in files/en-us/web/http/reference/methods/options/index.md was changed. No unrelated documentation files were modified.
Related issues and pull requests
Fixes #46204