2.2.2.3 Secure Clock Challenge POST Request
The client submits a secure clock challenge request to the secure clock challenge URL, retrieved from the petition response, and waits for the server's response. The secure clock challenge request is an HTTP/1.0 POST request as shown below:
-
POST ChallengePath HTTP/1.0 Accept: Accept: */* Content-Type: application/x-www-form-urlencoded Content-Length: 376 User-Agent: Client-User-Agent Proxy-Connection: Keep-Alive Pragma: no-cache
The client MUST be prepared to follow HTTP [RFC2616] redirections during the petition. If the secure clock server responds with HTTP 301 (Moved) or 302 (Redirect), the client MUST use this redirect URL as the new secure clock challenge URL and start again by submitting the secure clock challenge to the redirected URL.