플러터로 멀티플랫폼 프로그램 만드는데 안드로이드나 윈도우는 잘 잘동하는데 브라우저에서 get요청 보내면 요청에 어거지로 body 넣어도 브라우저에서 자동으로 칼질해서 보냄
원래 get 요청이 보통 body대신 url에 쿼리로 붙여서 보내는걸 알고는있는데 브라우저는 이게 강제인듯 파라미터 크기가 엄청 크거나 보안상 노출할수없는 값이면 무적권 post 써야함?
RFC 2616, section 4.3 clearly states:
A message-body MUST NOT be included in a request if the specification of the request method (section 5.1.1) does not allow sending an entity-body in requests.
https://tools.ietf.org/html/rfc2616#section-4.3
However, in the entirety of section 9.3, the section defining the GET verb, nothing prevents a GET request from having a body.
But before you draw any conclusions - the functionality defined for the GET verb also does not include any logic involving the message body.
In other words, if we are to follow the specification:
- It is possible to send a message body with a GET request per specification.
- However, the server responding to the GET request must ignore the body to follow the standard.
Essentially, there is no point, per standard, to send a body with a GET request, even though it is not explicitly disallowed.
Roy T. Fielding backs this interpretation up:
...any HTTP request message is allowed to contain a message body, and thus must parse messages with that in mind. Server semantics for GET, however, are restricted such that a body, if any, has no semantic meaning to the request. The requirements on parsing are separate from the requirements on method semantics.
So, yes, you can send a body with GET, and no, it is never useful to do so.
https://groups.yahoo.com/neo/groups/rest-discuss/conversations/messages/9962
스펙상 가능은 한데 브라우저는 표준을 지키기 위해 get의 바디를 무시한다고 되어있음...
브라우저에서 강제로 get으로 보내는법이 있을까
다른 플랫폼에선 잘되는데 웹버전 때문에 서버 수정하기가 먼가 불합리함
나는 get에 꼭 body 넣어야겠다면 애초에 get메서드 전부 post로 만들어도 되는거 아님?
