Доброволците ни все още не са превели статията на Български. Присъединете се и помогнете да свършим тая работа!
Можете да прочетете статията и на English (US).
The method and the body of the original request are reused to perform the redirected request. In the cases where you want the method used to be changed to
303 See Other instead. This is useful when you want to give an answer to a
PUT method that is not the uploaded resources, but a confirmation message (like "You successfully uploaded XYZ").
The only difference between
302 is that
307 guarantees that the method and the body will not be changed when the redirected request is made. With
302, some old clients were incorrectly changing the method to
GET: the behavior with non-
GET methods and
302 is then unpredictable on the Web, whereas the behavior with
307 is predictable. For
GET requests, their behavior is identical.
307 Temporary Redirect
|RFC 7231, section 6.4.7: 307 Temporary Redirect||Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content|
|Chrome Full support Yes||Edge Full support Yes||Firefox Full support Yes||IE Full support Yes||Opera Full support Yes||Safari Full support Yes||WebView Android Full support Yes||Chrome Android Full support Yes||Edge Mobile Full support Yes||Firefox Android Full support Yes||Opera Android Full support Yes||Safari iOS Full support Yes||Samsung Internet Android Full support Yes|
- Full support
- Full support