Spectrum Post CURL command for Subscription returns code 100

Products

• DX NetOps
• CA Spectrum

Issue/Introduction

When I submit the following curl command, the post is successful, and the subscription config is made, 

but the session does not end. The verbose response code is 100, and it is like it's expecting more input, but the post is done. 

not sure how to get a 200 response from this, or other means to terminate the http

Here's the following curl:

curl -v -u username:passwrd -X 'POST' \

  'https://reportmanager_hostname:8443/spectrum/restful/subscription' \

  -H 'accept: application/xml; charset=UTF-8' \

  -H 'Content-Type: application/xml; charset=UTF-8' \

  -d '<?xml version="1.0" encoding="UTF-8"?>

<rs:subscription-request         xmlns:rs="http://www.ca.com/spectrum/restful/schema/request"           xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"          xsi:schemaLocation="http://www.ca.com/spectrum/restful/schema/request ../../../Rest.a/src/xsd/Request.xsd"             send-preexisting-instances="false">

<rs:push-delivery-mode>

<!-- The destination URL must give a HTTP 200 SUCCESS response -->

<rs:destination-url>https://collectionserver_hostname:8443</rs:destination-url>

<!-- batch up to 100 alarms per push. Wait up to 1000 ms to fill batch -->

<rs:batch-notifications max-notifications="100" max-time="1000"/>

<!-- send a heartbeat message every 10 minutes -->

<rs:heartbeat-interval>600000</rs:heartbeat-interval>

</rs:push-delivery-mode>

<rs:alarm-request>

<!-- send all attributes -->

<rs:requested-attribute id="0x10000"/>

<rs:requested-attribute id="0x10001"/>

<rs:requested-attribute id="0x10009"/>

<rs:requested-attribute id="0x1000a"/>

 

</rs:alarm-request>

</rs:subscription-request>'

 

 

Here is the verbose output:

*cert and auth info deleted*

> POST /spectrum/restful/subscription HTTP/1.1
> User-Agent: curl/7.29.0
> accept: application/xml; charset=UTF-8
> Content-Type: application/xml; charset=UTF-8
> Content-Length: 2305
> Expect: 100-continue
> 
< HTTP/1.1 100 

 

from here it hangs open

Environment

Release : 21.2

Resolution

There was a delay in the processing. The customer let the command run and eventually it came back with a status of HTTP 200.