Why extra Request Methods generated?
See original GitHub issueI just wonder why I have OPTIONS, HEAD, PATCH while I don’t have any match RequestMapping(method = RequestMethod.
OPTIONS, HEAD, PATCH
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Why am I getting an OPTIONS request instead of a GET ...
According to MDN,. Preflighted requests. Unlike simple requests (discussed above), "preflighted" requests first send an HTTP OPTIONS request ...
Read more >HTTP Request Methods – Get vs Put vs Post Explained with ...
We use POST to create a new resource. A POST request requires a body in which you define the data of the entity...
Read more >[Chapter 17] 17.2 Client Requests
It is the most commonly used method by browsers to retrieve documents for viewing. The result of a GET request can be generated...
Read more >Advanced Usage — Requests 2.28.1 documentation
A Session object has all the methods of the main Requests API. ... Second, a Response object is generated once Requests gets a...
Read more >HTTP/1.1: HTTP Message
Certain buggy HTTP/1.0 client implementations generate extra CRLF's after a POST request. To restate what is explicitly forbidden by the BNF, an HTTP/1.1 ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@amorenew,
By default, @RequestMapping(“/topics”), allows all the HTTP methods which explains the result you got. You should precise your HTTP methods: for example: @GetMapping(“/topics”) …
@amorenew,
Can you provide with a sample code (HelloController) or Test that reproduces your behaviour?