The responses to some HTTP requests can be cached depending on the HTTP verb used in the request. According to the HTTP specification, for what HTTP verbs is this safe to do?
After seeing the many comments here and elsewhere, I was choosing option D, which is wrong. OPTIONS HTTP method is non-cacheable. The right answer is B. By default, POST HTTP method is non-cacheable but by adding Cache-Control headers, it can be made cacheable.
You are wrong. According to the official Mulesoft practice exam the correct answer is D. Don't ask me why, but that's the answer they have given so it should be right.
The answer is D. According to the HTTP specification, it is safe to cache responses for HTTP verbs GET, OPTIONS, and HEAD. This is because these requests are considered "safe" and do not modify or delete any resources on the server. Therefore, caching responses for these requests can improve performance and reduce the number of requests made to the server. However, caching responses for requests that modify or delete resources (such as PUT, POST, and DELETE) can cause issues and should be avoided.
B.
OPTIONS is not cacheable.
https://developer.mozilla.org/en-US/docs/Web/HTTP/Methods/OPTIONS
https://developer.mozilla.org/en-US/docs/Web/HTTP/Methods/POST
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
Neo_0000
6 months, 2 weeks agoAlandt
4 months agoFreedox
1 year, 5 months agovikas_mule
1 year, 7 months agocuisal92
1 year, 9 months agosirious09
1 year, 10 months agocalazans
2 years, 4 months agoFL107
2 years, 6 months agoOutdoor25
2 years, 10 months agoAB317
3 years, 2 months agoPavan_Nagineni
3 years, 3 months ago