You know how HTTP GET requests are meant to be idempotent?

Re:You know how HTTP GET requests are meant to be idempotent? by NewEntryHN on Tuesday May 01, 2018 @11:01AM (#16967539)

GET requests aren't supposed to be idempotent. They're not supposed to change state in a first place.

[ Parent | on HN ]

Re:You know how HTTP GET requests are meant to be idempotent? by dragonwriter on Tuesday May 01, 2018 @01:44PM (#16969364)

> GET requests aren't supposed to be idempotent.

RFC 7231 disagrees.

> They're not supposed to change state in a first place.

Well, yeah, GET is supposed to be safe, but all safe methods are also idempotent.

[ Parent | on HN ]

Re:You know how HTTP GET requests are meant to be idempotent? by CoolAndComposed on Tuesday May 01, 2018 @03:09PM (#16970350)

Just because a server announces HTTP/1.1 doesn't mean it conforms to that specific RFC.

[ Parent | on HN ]

Re:You know how HTTP GET requests are meant to be idempotent? by dragonwriter on Tuesday May 01, 2018 @03:36PM (#16970655)

That non-RFC-compliant implementations of HTTP exist irrelevant to what properties HTTP methods are supposed to have, which is the issue under discussion.

[ Parent | on HN ]

Re:You know how HTTP GET requests are meant to be idempotent? by CoolAndComposed on Friday May 04, 2018 @03:57PM (#16997734)

It is compliant to an RFC, just not a specific RFC. That's part of the issue, that's simply taken for granted because of ideology.

[ Parent | on HN ]