Jan 님의 답글
개발자 답글
7년 전에 게시됨Hi, 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개
- 5점 만점에 5점Firefox 사용자 19010092 님, 2달 전
- 5점 만점에 5점Firefox 사용자 17436936 님, 8달 전
- 5점 만점에 5점msajadi832 님, 일 년 전
- 5점 만점에 5점Firefox 사용자 15313516 님, 일 년 전
- 5점 만점에 5점Firefox 사용자 18253713 님, 2년 전
- 5점 만점에 5점Firefox 사용자 18115635 님, 2년 전
- 5점 만점에 5점Miguel Conde 님, 3년 전
- 5점 만점에 5점Firefox 사용자 12924248 님, 3년 전
- 5점 만점에 5점harl windwolf 님, 3년 전Excellent 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!
- 5점 만점에 5점felipecontrerass 님, 3년 전
- 5점 만점에 5점Firefox 사용자 14678933 님, 3년 전
- 5점 만점에 4점Firefox 사용자 17505828 님, 3년 전I 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 (?)개발자 답글
3년 전에 게시됨Sorry 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? - 5점 만점에 5점Firefox 사용자 17444643 님, 3년 전
- 5점 만점에 5점Mahdi Magroun 님, 4년 전
- 5점 만점에 5점Firefox 사용자 13329218 님, 4년 전
- 5점 만점에 5점Oleg Kyiashko 님, 4년 전