Protocols/MSNP/Gateway: Difference between revisions
(Created page with "Convert from markdown: <pre> Here is some information about the HTTP gateway used by Messenger if it fails to connect directly to the MSNP server (port 1863). ## Hosts ```...") |
Animadoria (talk | contribs) No edit summary |
||
| Line 1: | Line 1: | ||
Here is some information about the HTTP gateway used by Messenger if it fails to connect directly to the MSNP server (port 1863). | Here is some information about the HTTP gateway used by Messenger if it fails to connect directly to the MSNP server (port 1863). | ||
== Hosts == | |||
<pre> | |||
gateway.messenger.hotmail.com | gateway.messenger.hotmail.com | ||
muser.gateway.messenger.hotmail.com | muser.gateway.messenger.hotmail.com | ||
</pre> | |||
== Implementation == | |||
The gateway is jut a proxy for Messenger commands. | |||
The first request is a POST request to the URL | === First request === | ||
The first request is a POST request to the URL <code>/gateway/gateway.dll?Action=open&Server={server type}&IP={server the client tried to connect to}</code>. | |||
<code>{server type}</code> is either <code>NS</code> (Notification server) or <code>SB</code> (Switchboard server). | |||
The POST body is the | The POST body is the <code>VER</code> command. | ||
This first request should trigger the creation of a session ID in the database. This session ID will be present in the URLs of all subsequent requests to the gateway. | This first request should trigger the creation of a session ID in the database. This session ID will be present in the URLs of all subsequent requests to the gateway. | ||
This session ID along with the gateway IP address should be sent in an | This session ID along with the gateway IP address should be sent in an <code>X-MSN-Messenger</code> header: | ||
<code>"X-MSN-Messenger": "SessionID={session ID}; GW-IP={IP of the gateway service}"</code> | |||
A | A <code>Content-Type</code> header should be added as well: | ||
<code>"Content-Type": "application/x-msn-messenger"</code> | |||
The body of the response is simply the response to the command. | The body of the response is simply the response to the command. | ||
=== Subsequent requests === | |||
==== Type 1: <code>/gateway/gateway.dll?SessionID={session ID}</code> ==== | |||
The client wants to send a command to the server. The command is in the POST body. Answer with the command response and include the 2 headers as shown above. | The client wants to send a command to the server. The command is in the POST body. Answer with the command response and include the 2 headers as shown above. | ||
==== Type 2: <code>/gateway/gateway.dll?Action=poll&SessionID={session ID}</code>==== | |||
The client wants to know if the server has queued any specific command(s) for the current session. Answer with the specified command(s). If the client has no commands to poll, send an empty reply. Include the 2 headers. | The client wants to know if the server has queued any specific command(s) for the current session. Answer with the specified command(s). If the client has no commands to poll, send an empty reply. Include the 2 headers. | ||
</pre> | </pre> | ||
Revision as of 19:53, 2 May 2021
Here is some information about the HTTP gateway used by Messenger if it fails to connect directly to the MSNP server (port 1863).
Hosts
gateway.messenger.hotmail.com muser.gateway.messenger.hotmail.com
Implementation
The gateway is jut a proxy for Messenger commands.
First request
The first request is a POST request to the URL /gateway/gateway.dll?Action=open&Server={server type}&IP={server the client tried to connect to}.
{server type} is either NS (Notification server) or SB (Switchboard server).
The POST body is the VER command.
This first request should trigger the creation of a session ID in the database. This session ID will be present in the URLs of all subsequent requests to the gateway.
This session ID along with the gateway IP address should be sent in an X-MSN-Messenger header:
"X-MSN-Messenger": "SessionID={session ID}; GW-IP={IP of the gateway service}"
A Content-Type header should be added as well:
"Content-Type": "application/x-msn-messenger"
The body of the response is simply the response to the command.
Subsequent requests
Type 1: /gateway/gateway.dll?SessionID={session ID}
The client wants to send a command to the server. The command is in the POST body. Answer with the command response and include the 2 headers as shown above.
Type 2: /gateway/gateway.dll?Action=poll&SessionID={session ID}
The client wants to know if the server has queued any specific command(s) for the current session. Answer with the specified command(s). If the client has no commands to poll, send an empty reply. Include the 2 headers.