mirror of
https://github.com/cwinfo/envayasms.git
synced 2025-01-10 12:05:40 +00:00
header is now called X-Request-Signature
This commit is contained in:
parent
ec74941684
commit
53c60f8d24
@ -32,7 +32,7 @@ HTTP Request Format
|
||||
|
||||
<pre>
|
||||
POST /sg/EnvayaSMS HTTP/1.1
|
||||
X-EnvayaSMS-Signature: sAemG31uRllk/K9xck2WRNaF/WI=
|
||||
X-Request-Signature: sAemG31uRllk/K9xck2WRNaF/WI=
|
||||
Content-Length: 96
|
||||
Content-Type: application/x-www-form-urlencoded
|
||||
Host: 192.168.70.1:3000
|
||||
@ -45,7 +45,7 @@ from=6505551234&message_type=sms&message=test&version=2&phone_number=16505551212
|
||||
|
||||
<pre style='white-space:pre-wrap'>
|
||||
POST /sg/EnvayaSMS HTTP/1.1
|
||||
X-EnvayaSMS-Signature: OgpiQet9guVhEp+0klrONR8qGNs=
|
||||
X-Request-Signature: OgpiQet9guVhEp+0klrONR8qGNs=
|
||||
Content-Length: 13087
|
||||
Content-Type: multipart/form-data; boundary=i66xAht5IMn1Tfk7tL9DgY8ZHZxq0d0RGB6_wkjO
|
||||
Host: 192.168.70.1:3000
|
||||
@ -133,7 +133,7 @@ Content-Transfer-Encoding: binary
|
||||
|
||||
<pre>
|
||||
POST /sg/EnvayaSMS HTTP/1.1
|
||||
X-EnvayaSMS-Signature: 139CL71b7r1Zw/E2wcccWFviSlg=
|
||||
X-Request-Signature: 139CL71b7r1Zw/E2wcccWFviSlg=
|
||||
Content-Length: 50
|
||||
Content-Type: application/x-www-form-urlencoded
|
||||
Host: 192.168.70.1:3000
|
||||
@ -146,7 +146,7 @@ action=outgoing&version=2&phone_number=16505551212
|
||||
|
||||
<pre>
|
||||
POST /sg/EnvayaSMS HTTP/1.1
|
||||
X-EnvayaSMS-Signature: 6uJtI6+QqlVBbUsR4T0WsQomods=
|
||||
X-Request-Signature: 6uJtI6+QqlVBbUsR4T0WsQomods=
|
||||
Content-Length: 80
|
||||
Content-Type: application/x-www-form-urlencoded
|
||||
Host: 192.168.70.1:3000
|
||||
@ -211,7 +211,7 @@ The following parameters are sent in all POST requests from EnvayaSMS:
|
||||
The following HTTP Headers are sent in all POST requests from EnvayaSMS:
|
||||
|
||||
<dl>
|
||||
<dt>"X-EnvayaSMS-Signature" ::= <text></dt>
|
||||
<dt>"X-Request-Signature" ::= <text></dt>
|
||||
<dd>
|
||||
A signature of the request to verify the phone and the server share the same password.
|
||||
(This doesn't protect against MITM snooping or replay attacks, so it is recommended to
|
||||
|
@ -66,7 +66,7 @@ HTTP Request Format
|
||||
|
||||
<pre>
|
||||
POST /sg/EnvayaSMS HTTP/1.1
|
||||
X-EnvayaSMS-Signature: sAemG31uRllk/K9xck2WRNaF/WI=
|
||||
X-Request-Signature: sAemG31uRllk/K9xck2WRNaF/WI=
|
||||
Content-Length: 96
|
||||
Content-Type: application/x-www-form-urlencoded
|
||||
Host: 192.168.70.1:3000
|
||||
@ -79,7 +79,7 @@ from=6505551234&message_type=sms&message=test&version=2&phone_number=16505551212
|
||||
|
||||
<pre style='white-space:pre-wrap'>
|
||||
POST /sg/EnvayaSMS HTTP/1.1
|
||||
X-EnvayaSMS-Signature: OgpiQet9guVhEp+0klrONR8qGNs=
|
||||
X-Request-Signature: OgpiQet9guVhEp+0klrONR8qGNs=
|
||||
Content-Length: 13087
|
||||
Content-Type: multipart/form-data; boundary=i66xAht5IMn1Tfk7tL9DgY8ZHZxq0d0RGB6_wkjO
|
||||
Host: 192.168.70.1:3000
|
||||
@ -167,7 +167,7 @@ Content-Transfer-Encoding: binary
|
||||
|
||||
<pre>
|
||||
POST /sg/EnvayaSMS HTTP/1.1
|
||||
X-EnvayaSMS-Signature: 139CL71b7r1Zw/E2wcccWFviSlg=
|
||||
X-Request-Signature: 139CL71b7r1Zw/E2wcccWFviSlg=
|
||||
Content-Length: 50
|
||||
Content-Type: application/x-www-form-urlencoded
|
||||
Host: 192.168.70.1:3000
|
||||
@ -180,7 +180,7 @@ action=outgoing&version=2&phone_number=16505551212
|
||||
|
||||
<pre>
|
||||
POST /sg/EnvayaSMS HTTP/1.1
|
||||
X-EnvayaSMS-Signature: 6uJtI6+QqlVBbUsR4T0WsQomods=
|
||||
X-Request-Signature: 6uJtI6+QqlVBbUsR4T0WsQomods=
|
||||
Content-Length: 80
|
||||
Content-Type: application/x-www-form-urlencoded
|
||||
Host: 192.168.70.1:3000
|
||||
@ -245,7 +245,7 @@ The following parameters are sent in all POST requests from EnvayaSMS:
|
||||
The following HTTP Headers are sent in all POST requests from EnvayaSMS:
|
||||
|
||||
<dl>
|
||||
<dt>"X-EnvayaSMS-Signature" ::= <text></dt>
|
||||
<dt>"X-Request-Signature" ::= <text></dt>
|
||||
<dd>
|
||||
A signature of the request to verify the phone and the server share the same password.
|
||||
(This doesn't protect against MITM snooping or replay attacks, so it is recommended to
|
||||
|
Loading…
Reference in New Issue
Block a user