10 Aug
2016
10 Aug
'16
2:04 p.m.
On 2016-08-10 15:52, Cyrus Daboo wrote:
My impression was that this client is wrong by not formulating the last request with a Request-URI matching the encoding in the body.
At the very first CalConnect interop event (over 10 years ago) we ran into many problems with URL encoding in multistatus responses etc. What we have now behaves according to everyone else's reading of how things work. I am afraid the client will have to change, we are very unlikely to make any change ourselves as the impact on existing clients is unknown.
Sure ... thanks for the input. /Peter