Respuesta de Jan
Respuesta del desarrollador
publicado el hace 7 añosHi, thanks for taking the time to dig into this issue. Unfortunately it is by design and there is no way to fix it (that I know of).
RESTer is a browser extension and the browser provides two ways of sending HTTP requests:
1. XMLHttpRequest: This ignores any specified body and sets it to null when the method is GET or HEAD.
2. fetch: This throws a TypeError when you specifiy a body and the method is GET or HEAD.
Browsers have good reason to do so. While, according to the HTTP/1.1 spec, you are allowed to send a request body with a GET or HEAD request, the server is advised to ignore the body when handling the request. See here for a good explanation:
https://stackoverflow.com/a/983458/1798215
That said, if you have ideas on how to handle this better, please let me know. I am definitely open to suggestions. Post them on GitHub or send me an email:
https://github.com/frigus02/RESTer/issues
RESTer is a browser extension and the browser provides two ways of sending HTTP requests:
1. XMLHttpRequest: This ignores any specified body and sets it to null when the method is GET or HEAD.
2. fetch: This throws a TypeError when you specifiy a body and the method is GET or HEAD.
Browsers have good reason to do so. While, according to the HTTP/1.1 spec, you are allowed to send a request body with a GET or HEAD request, the server is advised to ignore the body when handling the request. See here for a good explanation:
https://stackoverflow.com/a/983458/1798215
That said, if you have ideas on how to handle this better, please let me know. I am definitely open to suggestions. Post them on GitHub or send me an email:
https://github.com/frigus02/RESTer/issues
105 revisiones
- Se valoró con 5 de 5por Usuario de Firefox 19010092, hace 3 meses
- Se valoró con 5 de 5por Usuario de Firefox 17436936, hace 9 meses
- Se valoró con 5 de 5por msajadi832, hace un año
- Se valoró con 5 de 5por Usuario de Firefox 15313516, hace un año
- Se valoró con 5 de 5por Usuario de Firefox 18253713, hace 2 años
- Se valoró con 4 de 5por Олексій, hace 2 añosOkay, but the JSON response fields containing text in Russian are displayed as strange characters.
- Se valoró con 5 de 5por Usuario de Firefox 18115635, hace 2 años
- Se valoró con 5 de 5por Erick, hace 2 años
- Se valoró con 5 de 5por Miguel Conde, hace 3 años
- Se valoró con 5 de 5por Usuario de Firefox 12924248, hace 3 años
- Se valoró con 5 de 5por harl windwolf, hace 3 añosExcellent add-on functionality, does exactly what I expected. Also, excellent description concerning its permissions, which provides the transparency that I'd wish to see with every add-on. Danke!
- Se valoró con 5 de 5por felipecontrerass, hace 3 años
- Se valoró con 5 de 5por Usuario de Firefox 14678933, hace 3 años
- Se valoró con 4 de 5por Usuario de Firefox 17505828, hace 3 añosI cannot install the add-on in Firefox (v103, Win 10 64bit).
I am installing from add-ons in firefox but it says "Installation aborted because the add-on is corrupted" and "This add-on is not actively monitored for security by Mozilla. Make sure you trust it before installing it."
while it is strange that on win8 32bit installed without a problem (?)Respuesta del desarrollador
publicado el hace 3 añosSorry for the late reply. I can't reproduce the issue, either. My best guess is that the file may got corrupted during download. Do you see the same issue after restarting Firefox? - Se valoró con 5 de 5por Xenthys, hace 3 años
- Se valoró con 5 de 5por Usuario de Firefox 17444643, hace 3 años
- Se valoró con 5 de 5por Roma657, hace 3 años
- Se valoró con 5 de 5por Mahdi Magroun, hace 4 años
- Se valoró con 5 de 5por Cyrille37, hace 4 años
- Se valoró con 5 de 5por Usuario de Firefox 13329218, hace 4 años
- Se valoró con 5 de 5por Oleg Kyiashko, hace 4 años