Hi people,
springfiles like most file servers only operates in HTTPS, but it seems to require HTTP ?
How can I tell the autohost to accept it ?
Cannot Upload a Map to autohost Heeeelp
Moderator: Moderators
Re: Cannot Upload a Map to autohost Heeeelp
update your download client?!
recent versions of pr-downloader support https. what are you using?
recent versions of pr-downloader support https. what are you using?
- Jonny5isalivetm
- Posts: 186
- Joined: 04 Jul 2006, 02:43
Re: Cannot Upload a Map to autohost Heeeelp
was trying to upload a map to techa main server its all good tho as was uploaded to a different server in the end which worked. HTTPS still an issue with main techa server tho
Re: Cannot Upload a Map to autohost Heeeelp
> HTTPS still an issue with main techa server tho
can you be more specific? what are you trying to do? is there an error message?
can you be more specific? what are you trying to do? is there an error message?
- Forboding Angel
- Evolution RTS Developer
- Posts: 14673
- Joined: 17 Nov 2005, 02:43
Re: Cannot Upload a Map to autohost Heeeelp
Perhaps he is talking about a spads plugin that allows users to upload maps to it? I do know there is a plugin for users to be able to feed a url to spads and it will download the file. Perhaps that is his issue. He is trying to give spads an https url and spads is saying Aw hell to the naw.
- Jonny5isalivetm
- Posts: 186
- Joined: 04 Jul 2006, 02:43
Re: Cannot Upload a Map to autohost Heeeelp
It was from springlobby to a autohost, using !dlmap command
It got worked out, some springfiles sites supported http and others only supported https
It got worked out, some springfiles sites supported http and others only supported https
- Silentwings
- Posts: 3720
- Joined: 25 Oct 2008, 00:23
Re: Cannot Upload a Map to autohost Heeeelp
Afaik SPADS is in the process of adopting https support (maybe its in dev but not release atm).
Re: Cannot Upload a Map to autohost Heeeelp
This command is not included in SPADS core but offered by the DownloadArchives plugin. The latest version of this plugin (0.4) should be fine with https links.Jonny5isalivetm wrote: ↑28 Jan 2020, 02:30 It was from springlobby to a autohost, using !dlmap command
Re: Cannot Upload a Map to autohost Heeeelp
TLS support for lobby connection is now available for all SPADS releases, but it's not enabled by default.Silentwings wrote: ↑28 Jan 2020, 08:00 Afaik SPADS is in the process of adopting https support (maybe its in dev but not release atm).
Re: Cannot Upload a Map to autohost Heeeelp
for the curious: why isn't pr-downloader used for downloading?
its understandable that a new dependency should be avoided. Spads uses perl and downloading a file is trivial: but for automatic updates of spring it seems to use a 7zip executable packed to it which could be replaced by pr-downloader which unpacks the engine, too. And then it could be used for maps and games downloads, too.
its understandable that a new dependency should be avoided. Spads uses perl and downloading a file is trivial: but for automatic updates of spring it seems to use a 7zip executable packed to it which could be replaced by pr-downloader which unpacks the engine, too. And then it could be used for maps and games downloads, too.
Re: Cannot Upload a Map to autohost Heeeelp
Actually I remember experimenting a bit with pr-downloader long time ago, unfortunately I wasn't able to use pr-downloader in a non-intrusive way (i.e. not modifying anything else than what was asked, in the location it was asked). I don't remember exactly which commands I tested and what were the exact problems at that time though. Maybe I just fell into the trap where specifying "--filesystem-writepath" after the action parameter ("--download-map", "--download-engine" for example) will partly ignore the provided writepath and create/use the default "$HOME/.spring/..." folders. Or maybe it was some Windows specific thing...
Also, SPADS uses a different directory structure than the one used by pr-downloader. pr-downloader uses "engine/<version>" whereas SPADS uses "spring/<version>-<architecture>". Afaik there is no way to tell pr-downloader to just extract the engine in a given folder, it will necessarily create the "engine/<version>" structure. SPADS uses the "<version>-<architecture>" name to recognize engines downloaded for different architectures (useful when SPADS files are moved from one system to another with different architecture...).
Finally, SPADS only extracts the required files for autohosting (spring-dedicated, spring-headless and base data), whereas pr-downloader extracts the full engine each time.
Also, SPADS uses a different directory structure than the one used by pr-downloader. pr-downloader uses "engine/<version>" whereas SPADS uses "spring/<version>-<architecture>". Afaik there is no way to tell pr-downloader to just extract the engine in a given folder, it will necessarily create the "engine/<version>" structure. SPADS uses the "<version>-<architecture>" name to recognize engines downloaded for different architectures (useful when SPADS files are moved from one system to another with different architecture...).
Finally, SPADS only extracts the required files for autohosting (spring-dedicated, spring-headless and base data), whereas pr-downloader extracts the full engine each time.