Antwurd fan Jan
Antwurd ûntwikkeler
8 jierren lyn pleatstHi, 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
108 beoardielingen
- Wurdearring: 5 fan 5troch Daniel V. Lenskiy, 3 moannen lyn
- Wurdearring: 5 fan 5troch Seän "frostbyte" Shepherd, 7 moannen lyn
- Wurdearring: 5 fan 5troch Firefox-brûker 19010092, ien jier lyn
- Wurdearring: 5 fan 5troch Firefox-brûker 17436936, 2 jierren lyn
- Wurdearring: 5 fan 5troch msajadi832, 2 jierren lyn
- Wurdearring: 5 fan 5troch Firefox-brûker 15313516, 2 jierren lyn
- Wurdearring: 5 fan 5troch Firefox-brûker 18253713, 2 jierren lyn
- Wurdearring: 4 fan 5troch Олексій, 2 jierren lynOkay, but the JSON response fields containing text in Russian are displayed as strange characters.
- Wurdearring: 5 fan 5troch Firefox-brûker 18115635, 3 jierren lyn
- Wurdearring: 5 fan 5troch Erick, 3 jierren lyn
- Wurdearring: 5 fan 5troch Miguel Conde, 3 jierren lyn
- Wurdearring: 5 fan 5troch Firefox-brûker 12924248, 4 jierren lyn
- Wurdearring: 5 fan 5troch harl windwolf, 4 jierren lynExcellent 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!
- Wurdearring: 5 fan 5troch felipecontrerass, 4 jierren lyn
- Wurdearring: 5 fan 5troch Firefox-brûker 14678933, 4 jierren lyn
- Wurdearring: 4 fan 5troch Firefox-brûker 17505828, 4 jierren lynI 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 (?)Antwurd ûntwikkeler
4 jierren lyn pleatstSorry 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? - Wurdearring: 5 fan 5troch Xenthys, 4 jierren lyn
- Wurdearring: 5 fan 5troch Firefox-brûker 17444643, 4 jierren lyn
- Wurdearring: 5 fan 5troch Roma657, 4 jierren lyn
- Wurdearring: 5 fan 5troch Mahdi Magroun, 4 jierren lyn