Closed GoogleCodeExporter closed 9 years ago
Yes, probably this has been missed. I was not aware of that because I've just
used my custom implementation at this time.
The SCEP draft indicates that an SCEP server might response with an HTTP 5xx
error if this operation is not supported. The client should treat this
operation as not supported. That's the case with the Entrust implementation.
A more or less "draft ready" patch is attached:
Client.patch:
Catch the IOException and check for HTTP 5xx error. If that's the case just put
empty capabilities in cache.
Capabilities.patch:
Add method clear();.
Original comment by nikolas....@gmail.com
on 26 Dec 2011 at 5:30
Attachments:
Looks promising. But still failed to catch the message thrown by this SCEP
server. I believe this line:
if (e.getMessage().contains("HTTP/1.0 5")) {
should be:
if (e.getMessage().contains("500") || e.getMessage().contains("502")) {
Original comment by michal.m...@gmail.com
on 27 Dec 2011 at 5:17
This issue was closed by revision r1330.
Original comment by da...@grant.org.uk
on 19 Jan 2012 at 8:18
Original comment by da...@grant.org.uk
on 22 Mar 2012 at 8:43
Original comment by da...@grant.org.uk
on 21 Aug 2012 at 11:58
Original issue reported on code.google.com by
michal.m...@gmail.com
on 25 Dec 2011 at 10:21