[Feature Request] Server Transfer

[pkurras]

SSGs launcher provides the option to initiate server transfers from the UI.
It'd be great if OneLauncher includes this feature into its own UI.

[JuneStepp]

I'm not implementing this right now, but I did do some investigation. Here are my notes:

The game launcher config (see src/onelauncher/game_launcher_config.py) has the following information about trasnfers:

• ShardTransfer.Enabled
  • Raise error that transfers are currently disabled when this is False.
• ShardTransfer.GuideURL
  • See if this should be provided to the user.
  • DDO does not have this.
• ShardTransfer.StoreURL
  • Currently is another guide that may be more up to date. There may be guides that are more up to date than both of these currently.
  • DDO's goes to a dead link.
• ShardTransfer.ServiceURL: The SOAP endpoint for doing transfers.

ShardTransfer.ServiceURL is currently http://xfer.lotro.com/TurbineTransferService/TurbineTransferService.svc for LOTRO. Requests to this URL will get a 301 Moved Permanently redirect response to the same URL but https. Following the redirect with follow_redirects in https does not work, because the request type is changed to GET. This is due to it being a 301 redirect rather than 308. Here is an example SOAP request:

content = b"""
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
    xmlns:tem="http://tempuri.org/">
    <soapenv:Header />
    <soapenv:Body>
        <tem:GetTransferConfiguration />
    </soapenv:Body>
</soapenv:Envelope>
"""

httpx_client.post(
	"https://xfer.lotro.com/TurbineTransferService/TurbineTransferService.svc",
	headers={
		"SOAPAction": "http://tempuri.org/TurbineTransferService/GetTransferConfiguration",
		"Content-Type": "text/xml; charset=utf-8"
	},
	content=content)

Unlike the other SOAP endpoints, doing a GET request to {ENDPOINT}?WSDL does not work. The WSDL data is only exposed via MEX (WS-MetadataExchange). Here is an example request to get the metadata:

content = b"""
<s:Envelope
    xmlns:a="http://www.w3.org/2005/08/addressing"
    xmlns:s="http://www.w3.org/2003/05/soap-envelope">
    <s:Header>
        <a:Action
            s:mustUnderstand="1">
            http://schemas.xmlsoap.org/ws/2004/09/transfer/Get
        </a:Action>
        <a:ReplyTo>
            <a:Address>
                http://www.w3.org/2005/08/addressing/anonymous
            </a:Address>
        </a:ReplyTo>
        <a:To
            s:mustUnderstand="1">
            http://xfer.lotro.com/TurbineTransferService/TurbineTransferService.svc/mex
        </a:To>
        <a:MessageID>
            urn:uuid:5387a7b5-ba52-419e-9a62-ab2b98280888
        </a:MessageID>
    </s:Header>
    <s:Body />
</s:Envelope>
"""

httpx_client.post(
    "https://xfer.lotro.com/TurbineTransferService/TurbineTransferService.svc/mex",
    headers={"Content-Type": "application/soap+xml; charset=utf-8"},
    content=content)

Notice the endpoint has /mex appended.

Unfortunately, this does not return a single WSDL document that can be directly given to Zeep. It returns a series of MetaDataSections that include both the TurbineTransferService WSDL, the http://www.turbine.com/SE/Bindings WSDL it imports, and multiple schemas that are used by those.

Given the relatively large size of the metadata and the transfer services tendency to be hard to access, it would be especially wise to cache this or even pre-ship it as the base for #309 (internal issue tracker). I got either 503 errors or super long reads that would pass any normal timeout frequently.

Besides the SOAP stuff, there's also this file available.

The GetPointBalance and GetAllCharacters operations could be useful for features beyond transfers.