Context Navigation

Changes between Initial Version and Version 1 of Ticket #11687, comment 3

initial	v1
1	1	I'm not sure this is a good solution. Now, the request will behave irrationally on a redirect when you use a non-seekable stream.
	2
	3	One would need some kind of callback mechanism in order to deal with that case (and eventually reset the input stream manually there). It might also be interesting for the initiator to know whether a redirect happened or not, in any case.
	4
	5	Also, if we had a specific callback for the rewind case (which could default to rewinding a seekable stream), we could also add buffering the input data up to a certain size at any time.