Can't use http-cache with un-cloneable requests about http-cache

[06chaynes]

Yes, the request would need to be cloned so if you're dealing with a situation where that's not possible I would recommend removing the middleware for now.

[06chaynes]

Thought about this a bit more and I could possibly add a new method that would be called in the middleware implementation before the run method call to determine if the request is cacheable or not, then maybe just continue the chain normally rather than calling the run method. This would at least allow those requests determined non cachable to proceed without needing to be cloned.

[06chaynes]

@joolean not sure if you'd be interested in the details but I made a branch to test this change. Still looking things over and testing but I think it should work for your purposes in its current state. If it's determined to be a cacheable request then the logic would still run and error if a clone isn't possible, but now if it's determined to not be a cacheable request it the client implementation should run without cloning the request.

[06chaynes]

Just FYI I finished up these changes and merged this into develop, so it'll be in the next release. This still can't work with requests that can't be cloned and determined to be cacheable but now it should at least work in those situations where it's determined to not be cacheable. Hope this update helps out!

[joolean]

Thanks for working on this @06chaynes! This sounds like it'll address my use case quite well. I've been busy with work but will try out the new release as soon as it's ready.

[06chaynes]

Sounds good! Just published the new versions so should be good to test whenever. Feel free to let me know if you have any issues!