Andrei Neculau

client & cache diagram

6

it is not only the server that can benefit from an FSM to decide the HTTP response flow, but also the client ~~and the cache proxy (a version is already...

see https://github.com/for-GET/http-decision-diagram/issues/50#issuecomment-340272642

http://tools.ietf.org/html/draft-ietf-httpbis-p5-range https://tools.ietf.org/html/draft-ietf-httpbis-p4-conditional-26#section-6

http://for-get.github.io/http-decision-diagram/httpdd.fsm.html - [ ] keep/switch from jointjs - [ ] elements should be read-only - [ ] view should be scalable - [ ] view should be closer (visually) to...

dispatch uri vs resource uri

1

the resource should probably be self-aware of the path it is instantiated on, otherwise it's impossible for it to produce a response with a rel=self link it could also just...

CORS support

1

CORS is rather common `process_options : in` should call specific callbacks for setting `access-control-*` headers

301&302 vs 307&308

2

given 307 & 308, is there a good reason beyond “legacy” compatibility to support 301 & 302? the diagram went KISS and chose 307 & 308 in https://github.com/for-GET/http-decision-diagram/commit/49cc4b703c7c67239bea9904b2ac1a162a475196

Override some HTTP statuses

2

Some HTTP statuses may leak out information, so it's better to alter them. While one can do so in override, maybe there should be a more specific way to override...