Error while attempting to update SNTP Settings via conduit web API.

Home Forums Conduit: AEP Model Error while attempting to update SNTP Settings via conduit web API.

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #30548
    Ajay K
    Participant

    in an attempt to automate few of our conduit setup processes, I am trying to update the SNTP settings via the Conduit Web API. Here is a put request to update the conduit settings and I get an HTTP Error of 417. Please see the raw request and response as noted in fiddler and I was wondering why is the conduit API throwing this error? Even if I send a partial object or a complete SNTP object I get the same error.

    Request:

    PUT https://192.168.2.1/api/sntp?token=22279F7A1095B2F64E9AF9E93A161138 HTTP/1.1
    Content-Type: application/json; charset=utf-8
    Host: 192.168.2.1
    Cookie: token=22279F7A1095B2F64E9AF9E93A161138
    Content-Length: 91
    Expect: 100-continue

    {“enabled”:true,”pollingTime”:120,”servers”:[“time.nist.gov”,””,””,””,””],”timeZone”:”UTC”}

    Response:

    HTTP/1.1 417 Expectation Failed
    Content-Type: text/html
    Content-Length: 363
    Connection: close
    Date: Tue, 21 Apr 2020 01:02:09 GMT
    Server: rcell

    <?xml version=”1.0″ encoding=”iso-8859-1″?>
    <!DOCTYPE html PUBLIC “-//W3C//DTD XHTML 1.0 Transitional//EN”
    http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd”&gt;
    <html xmlns=”http://www.w3.org/1999/xhtml&#8221; xml:lang=”en” lang=”en”>
    <head>

    Thanks,
    Ajay.

    #30549
    Jeff Hatch
    Keymaster

    Hello Ajay,

    Have you used the Expect header previously with the API. I don’t think that the server on Conduit is set up to handle Expect.

    Jeff

    #30550
    Ajay K
    Participant

    Thanks Jeff, I was using c# httpclient to send the put request and the extra header of Expect header was being sent and I removed it and it works fine now. Thanks for your help as always.

    Thanks,
    Ajay

Viewing 3 posts - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.