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
|app_id `String`|**Required** <br> The Pusher application ID |
63
+
|key `String`|**Required** <br> The Pusher application key |
64
+
|secret `String`|**Required** <br> The Pusher application secret token |
65
+
|host `String`|**Default:`None`** <br> The host to connect to |
66
+
|port `int`|**Default:`None`** <br>Which port to connect to |
67
+
|ssl `bool`|**Default:`False`** <br> Use HTTPS |
68
+
|cluster `String`|**Default:`None`** <br> Convention for other clusters than the main Pusher-one. Eg: 'eu' will resolve to the api-eu.pusherapp.com host |
69
+
|backend `Object`| an object that responds to the send_request(request) method. If none is provided, a `python.sync.SynchronousBackend` instance is created. |
In order for users to subscribe to a private- or presence-channel, they must be authenticated by your server.
165
190
166
191
The client will make a POST request to an endpoint (either "/pusher/auth" or any which you specify) with a body consisting of the channel's name and socket_id.
167
192
168
-
Using your `Config` instance, with which you initialized `Pusher`, you can generate an authentication signature. Having responded to the request with this signature, the subscription will be authenticated.
193
+
Using your `Pusher` instance, with which you initialized `Pusher`, you can generate an authentication signature. Having responded to the request with this signature, the subscription will be authenticated.
169
194
170
195
|Argument |Description |
171
196
|:-:|:-:|
@@ -182,8 +207,7 @@ Using your `Config` instance, with which you initialized `Pusher`, you can gener
If you have webhooks set up to POST a payload to a specified endpoint, you may wish to validate that these are actually from Pusher. The `Config` object achieves this by checking the authentication signature in the request body using your application credentials.
241
+
If you have webhooks set up to POST a payload to a specified endpoint, you may wish to validate that these are actually from Pusher. The `Pusher` object achieves this by checking the authentication signature in the request body using your application credentials.
220
242
221
-
#### `Config::validate_webhook`
243
+
#### `Pusher::validate_webhook`
222
244
223
245
|Argument |Description |
224
246
|:-:|:-:|
@@ -233,7 +255,7 @@ If you have webhooks set up to POST a payload to a specified endpoint, you may w
233
255
##### Example
234
256
235
257
```python
236
-
webhook = pusher.config.validate_webhook(
258
+
webhook = pusher.validate_webhook(
237
259
238
260
key="key_sent_in_header",
239
261
@@ -253,4 +275,4 @@ To run the tests run `python setup.py test`
253
275
License
254
276
-------
255
277
256
-
Copyright (c) 2014 Pusher Ltd. See LICENSE for details.
278
+
Copyright (c) 2015 Pusher Ltd. See LICENSE for details.
0 commit comments