Page History

...

• Risk of the issues this KIP address being dependant on KIP-82, and as KIP-82 is more contentious risks not dealing with the immediate issue for the next release
  • This could always be re-worked in future to use a header in a future release.

Note: If KIP-82 gets agreed on and merged and solution agreed upon lends itself to server side being header aware (aka not a client only wrapper) in time, we should re-evaluate this solution instead of the current proposed