Modpack Location Problem

[Lavious]

I'm using the new platform for the first time.  For many months the modpack location http://yaysoft.com/yaycraft/yaycraft.zip worked to download my pack from.

The zip file for my custom modpack is still accessible from that address. Yet, when I try to edit my modpack now, I am met with "The Modpack Location you entered is not a valid location." error.

 

What is wrong with downloading from that location?

[plowmanplow]

I've asked about it in #technic (IRC). As far as I can tell that URL is valid, is not using a redirect, and responds correctly using PHP's get_headers() call. Will follow up with a reponse if one is provided.

 

Edit 1: So, I looked at the pack contents. Why on earth are you making a system to do pack updates out of band from the Technic Launcher?? You should be using the Launcher for updates, and if you want to be more elaborate you should be implementing the Solder API for multiple versions and such. Expecting folks to use those batch files is quite unreasonable.

Edited January 11, 2015 by plowmanplow

[Lavious]

Because this is for a private pack with me and a few of my friends. The batch file updating process was at the request of everyone on the server. When this pack was implemented(somewhere 6 months ago) Solder API was not a thing I was aware of.  I'm not looking to edit the way we have been running our 1.6.4 but may be exploring the newer methods as I stark working with building a new pack for 1.8.  

 

What I am looking for, is to be able to use my domain http://yaysoft.com/yaycraft/ to host files.  Which i am having an issue with.

 

Considering how quickly the 'edit modpack' errors out, I expect the content of the ZIP file is irrelevant.

 

(Image below the error I am getting. Image below, is hosted on http://yaysoft.com/yaycraft/Capture.PNG so I am baffled.

 

[plowmanplow]

After some discussion in the IRC channel, the thoughts are that something odd may be configured in your web server which is not responding to all clients in a standards compliant way (or at least the way that the Platform is hitting the download URL). What web server are you using? Have you done anything unique or custom with the setup?