You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Yes I am facing same issue, and I am using the GCM client library as provided by google, which basically tries to make a HTTPS call to the endpoint https://android.googleapis.com/gcm/send to basically send a Multicast request.
The cottonballs responds on the same call but with HTTP protocol, it is really not understood what happens, as response is expected from the HTTPS binding and not HTTP binding.
Changing the GCMS library is not possible as it doesn't allow to send request to another URLs or using another protocols.
Hi, since cottonballs was built for performance testing, HTTPS/SSL was secondary - however there is support for it. did you follow the instructions regarding setting up SSL in the README?
techgaun
pushed a commit
to techgaun/cottonballs
that referenced
this issue
Feb 28, 2015
{
"registration_ids" : ["APA91bHpPg5OHGQswCT3FMv4MkdEbm2J2WEzuf69HlMljPvi_7htN3dlaZXCYReGGwDvtnoxw_TsaX0mY63x_htxdFrPvlWbnxUhIEKtbARAjCrbSXueIk6W66dw6zUBvEaSufZf4hSa_XQu5WpfzzYYmKy8OPFZyA", "ssghgshgsshg"],
"data" : {
"message":"Hello World from Watson!!"
}
}
We get response status 0.
The text was updated successfully, but these errors were encountered: