3 ms·
By adding the new verb, it implicitly formalizes that body in GET should not be used. Previously it was allowed, although not always expected. This may be a go
by Too 3y ago
By adding the new verb, it implicitly formalizes that body in GET should not be used. Previously it was allowed, although not always expected.
This may be a good thing and it could also be a bad thing if middleware starts relying on this new expectation and break old applications that previously assumed get bodies to be passed through.
They should clarify the expected behavior of GET bodies more explicit, whether it is allowed or not doesn’t really matter, as long as it is crystal clear.