handle Content-Location header
andreineculau opened this issue · comments
Andrei Neculau commented
Currently the diagram is unaware of this header, for none of the flows/methods, although this is a very good way of minimizing round-trips.
Ref: http://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-22#section-3.1.4.2
Andrei Neculau commented
one can override to_content
and handle this scenario there
Andrei Neculau commented
the diagram (not so much visually, but its to_content
docs) supports content-location
now