Skip to content
This repository has been archived by the owner on Apr 22, 2022. It is now read-only.

curl #17

Closed
anothergituser opened this issue Mar 20, 2016 · 5 comments
Closed

curl #17

anothergituser opened this issue Mar 20, 2016 · 5 comments

Comments

@anothergituser
Copy link

Does it support curl?

@dimiro1
Copy link
Owner

dimiro1 commented Mar 20, 2016

I did not understand. Can you explain?

@anothergituser
Copy link
Author

My bad, i meant something like
curl -HContent-Type:application/json -d '{"name":"my_event","channel":"DHVMDYGF","data":"hello world"}' "http://api.pusherapp.com/apps/1480/events?auth_key=765ec374ae0a69f4ce44&auth_signature=da1721ed1663534f741f6a6a6652f08aec10f9e3a407bd1fd9560cb6cf145888&auth_timestamp=1458508975&auth_version=1.0&body_md5=76382888869197021f94a3ae4ca6ca50"

Taken from pusher homepage..
Anyhow, this was silly, i'm closing the issue
Nice work 👍

@dimiro1
Copy link
Owner

dimiro1 commented Mar 20, 2016

Yes it works, but you have to change http://api.pusherapp.com/apps/1480/events to http://localhost:8080/apps/APP_ID/events and the other parameters auth_key, auth_signature.

@anothergituser
Copy link
Author

Hello again,

Im getting a lot of
E0321 17:35:22.063197 16975 connection.go:32] Error publishing message to connection &{SocketID:4845958082036516270.6455852401554598156 Socket:0xc8201a2300 CreatedAt:2016-03-21 17:31:52.370930416 +0100 CET}, websocket: close sent
in my console.
Other than that everything just works.
Anything of importance?
Thanks

@dimiro1
Copy link
Owner

dimiro1 commented Mar 21, 2016

It looks like a message is being sent to a closed websocket. Can you explain how you are using the software?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants