02-21-2014 11:05 AM
I got the credentials approved, service is ACTIVE on my server, and PushCollector from Cascades samples app repository is configured properly and ready.
However, I wanted to test out and send a push to a subscriber and this is what I get:
Please correct the following error(s): Unable to parse the response from this command because the content-type header field returned was not the expected: 'application/xml'. This may occur if the URL being accessed is wrong or the service at the URL is not available. Actual content-type returned was: text/html. Please check application log files for more information.
What URL? Docs are very vague, please can someone clarify. I'd like to make a clean detail exampl eof how to setup everything to enable push notification service.
Solved! Go to Solution.
02-21-2014 01:43 PM
Could you provide some more details on what steps you are taking to reproduce the below issue?
What are you using for your server-side? What URL are you sending the push payload to?
02-21-2014 02:21 PM
Sorry! I seem to keep splicing the message when I move it. I'm going to delete the other threads.
Here's my original, second, reply:
Ok, we'll get everything straightened around here, no worries
First thing: The URL for the PPG is correct but you need to append the suffix for the service:
Try that out and see if it fixes the error, if not let me know what happens.
02-21-2014 02:30 PM
I'm sorry, where exactly should I use that suffix?
Server side has no such input, at least I don't see it where I can modifiy the request in High Level Sample installed with BPSS.
On client side I tried adding that suffix but the same error is still the same.
02-21-2014 02:33 PM
02-21-2014 02:42 PM
I was asked to enter PPG url on BPSS install and never asked again.
Is there a way to modify it or do I have to reinstall BPSS to supply it with correct url?
BTW why did Eval Credentials email supply an incorrect PPG URL then?
02-21-2014 02:43 PM
I believe there may be an XML file where you can update this value...I normally just use a standard HTTPS POST app opposed to the entire SDK though.
The email includes the correct PPG URL, but various calls use different suffixes.
02-21-2014 03:06 PM
That URL I pasted directly from Low Level Sample provided by BPSS Linux binary file.
I used both unmodified High Level and Low Level samples and they still fail.
Even after I modifed all URLs to HTTPS in ../WEB-INF/classes/PushSDK.properties
Not to mention that PPG URL is not acceptable in PushCollector Cascades sample when it's in HTTPS. it explicitly demands a HTTP.
can you provide more detail in Private Message about exact POS/GET calls including their parameters. I can handle raw requests, I even prefer them but I cannot find any docs on exact request.