Anyone? I went to the sender API tab on the variants screen and copied the CURL UPS Rest command and ran it.

It failed. So clearly not a problem with the java client software I wrote. Clearly a problem with the push server. Does this function even work? Does anyone have it working? Why would it fail? Could it be that the settings are wrong in the server?

curl -u "48f23d56-75a5-4a7f-a097-a62404e5a6e0:221a9e9f-a040-4111-96b1-1d1983576f56"  \
   -v -H "Accept: application/json" -H "Content-type: application/json"  \
   -X POST  -d \
  '{
     "message": {
      "alert": "Hello from the curl HTTP Sender!",
      "sound": "default"
     }
   }'  \
   https://www.dealerrewards.com:8986/ag-push/rest/sender

Note: Unnecessary use of -X or --request, POST is already inferred.
*   Trying 173.166.153.1...
* Connected to www.dealerrewards.com (173.166.153.1) port 8986 (#0)
* ALPN, offering http/1.1
* Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
* successfully set certificate verify locations:
*   CAfile: C:\Users\Chris\AppData\Local\Apps\cURL\bin\curl-ca-bundle.crt
CApath: none
* TLSv1.2 (OUT), TLS header, Certificate Status (22):
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Client hello (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS change cipher, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-RSA-AES128-SHA256
* ALPN, server did not agree to a protocol
* Server certificate:
*        subject: OU=Domain Control Validated; OU=Free SSL; CN=www.dealerrewards.com
*        start date: Aug 16 00:00:00 2016 GMT
*        expire date: Nov 14 23:59:59 2016 GMT
*        subjectAltName: www.dealerrewards.com matched
*        issuer: C=GB; ST=Greater Manchester; L=Salford; O=COMODO CA Limited; CN=COMODO RSA Domain Validation Secure Server CA
*        SSL certificate verify ok.
* Server auth using Basic with user '48f23d56-75a5-4a7f-a097-a62404e5a6e0'
> POST /ag-push/rest/sender HTTP/1.1
> Host: www.dealerrewards.com:8986
> Authorization: Basic NDhmMjNkNTYtNzVhNS00YTdmLWEwOTctYTYyNDA0ZTVhNmUwOjIyMWE5ZTlmLWEwNDAtNDExMS05NmIxLTFkMTk4MzU3NmY1Ng==
> User-Agent: curl/7.46.0
> Accept: */*
> Accept : application/json
> Content-type : application/json
> Content-Length: 25
> Content-Type: application/x-www-form-urlencoded
>
* upload completely sent off: 25 out of 25 bytes
< HTTP/1.1 400 Bad Request
< Connection: keep-alive
< X-Powered-By: Undertow/1
< Server: WildFly/8
< Content-Type: text/html;charset=UTF-8
< Content-Length: 70
< Date: Wed, 17 Aug 2016 19:17:21 GMT
<
<html><head><title>Error</title></head><body>Bad Request</body></html>* Connection #0 to host www.dealerrewards.com left intact

Christopher Fahey
DealerRewards, Inc.
Maryland Branch Office
(410) 924-3185

This electronic message transmission contains information from DealerRewards Inc. This message is confidential. It may also be privileged or otherwise protected by work-product immunity or other legal rules. If you have received it by mistake, please let us know by email reply and delete it from your system; you may not copy this message or disclose its contents to anyone.
DISCLAIMER: Since 2006, the U.S. Government has been monitoring all internet communications. If you have information that you do not wish to have monitored, please send it using regular postal services to the address listed on our website.