Update for https?

[Wixoss_batoru]

Hello,

Dropbox recently changed their system and now enforces https instead of http, so links like http://dl.dropboxusercontent.com/s/*** don't work anymore in lackkey for plugin updates. Links like http://dl.dropboxusercontent.com/u/ available to older dropbox accounts still work but you can't telle when they'll also go 100% https there. Also, it's becoming harder and harder to find file hosting services that allows simple http

Do you plan to update LackeyCCG so that it can support https ?

[Trevor]

I'll fix this now.

[Wixoss_batoru]

Thank you !

[Trindall]

I think I'm running into this problem and I'm not sure if you've been able to patch in https support into the client yet.

I'm attempting to install the plugin using my public dropbox folder but get an immediate "Error: timed out while updating the plugin." response and nothing else.

I get this regardless of whether I use the https://dl.dropboxusercontent.com/u/ or http://dl.dropboxusercontent.com/u/ version of the updatelist.txt URL.

I've tried changing the URLs inside the updatelist.txt to have either all https:// references and with them all using the original http:// values.  (Since the plugin files are hosted in my public dropbox account.)

Could the timeout when installing the plugin be due to https support not in the client yet or possibly something else?

[Trevor]

I think I'm running into this problem and I'm not sure if you've been able to patch in https support into the client yet.

I'm attempting to install the plugin using my public dropbox folder but get an immediate "Error: timed out while updating the plugin." response and nothing else.

I get this regardless of whether I use the https://dl.dropboxusercontent.com/u/ or http://dl.dropboxusercontent.com/u/ version of the updatelist.txt URL.

I've tried changing the URLs inside the updatelist.txt to have either all https:// references and with them all using the original http:// values.  (Since the plugin files are hosted in my public dropbox account.)

Could the timeout when installing the plugin be due to https support not in the client yet or possibly something else?

Can you talk to me on Skype so we can make sure https works? I'm trevoragnitti on Skype.

[Trindall]

I've got a text to you on Skype for when you are free, my username is "trindall_".  I'm happy to help out if I can.

[Trevor]

Test the new version I just released today.

[Trindall]

Same response, "Error: timed out while updating the plugin."

I'm using the client that shows Build Date: 07-12-14 updated through the updater and I've also downloaded a fresh copy to a different location from the LackeyCCGBetaWin.zip file from your main page.

Of the three updatelist files I've modified the
https://dl.dropboxusercontent.com/u/7427384/LBPTCG/High/updatelist.txt
file to contain https references to all the files needed while the Maximum and Medium files still all have http references from what used to work.

Are you able to load up the plugin using the
https://dl.dropboxusercontent.com/u/7427384/LBPTCG/High/updatelist.txt
URL in your dev environment?

[Trevor]

Same response, "Error: timed out while updating the plugin."

I'm using the client that shows Build Date: 07-12-14 updated through the updater and I've also downloaded a fresh copy to a different location from the LackeyCCGBetaWin.zip file from your main page.

Of the three updatelist files I've modified the
https://dl.dropboxusercontent.com/u/7427384/LBPTCG/High/updatelist.txt
file to contain https references to all the files needed while the Maximum and Medium files still all have http references from what used to work.

Are you able to load up the plugin using the
https://dl.dropboxusercontent.com/u/7427384/LBPTCG/High/updatelist.txt
URL in your dev environment?

I was able to use https://dl.dropboxusercontent.com/u/7427384/LBPTCG/High/updatelist.txt with no problems on my computer. I'll try it from my virgin-state windows computer.

[Jynks]

opps.. sorry for double post.. I didn't see this.. looks like you guys are on it.. please ignore my other thread!

[Trevor]

It appears to work for me. Anyone still have a problem?

[Jynks]

I can nto work out where to download the test versions... I grabbed the one from the official download page on the website.. but they did not work.

I think you should delete ALL those threads or archive them or somthing and make a new thread.. that is locked for TEST VERSIONS and just update the thread with a edit.. and have a seprate conversation thread linked form there.

I have just spent nearly 15 mins and I can nto find a single link to download! Also at the end of every thread was a link to a new thread!! so confusing

Can you please post a link to the version that is supposed to work?

This is the link I am using
https://dl.dropboxusercontent.com/u/9169569/LackeyCCG/LoTR-LCG/updatelist.txt

Even changing the HTTPS tp HTTP dosn't seam to help

[r0cknes]

I have the same problem Windows Vista 64 bit. I also tried it on a windows 7 and that didn't work either.

[Trindall]

I can nto work out where to download the test versions... I grabbed the one from the official download page on the website.. but they did not work.

Out for a few days on holiday and back to see what I can do to help out on this problem.

I didn't think until your post that there may be a dev type build that I should test regarding the https support.  On the day that Trevor said that he thought he fixed it, 7/13/14 there was also an update for the client that downloaded via the update tool.

On that version, and the version I can get from the lackeyccg main web page both are still not working for me with https Dropbox locations.  I've tried it on my home and work computer but it could be that I'm not using the correct version of the client to test this out.  Possibly?

I've been trying to poke at this with WireShark while the request is done in LackeyCCG but there isn't much information.  If I try to use the older http:// version of the updatelist.txt I can see that LackeyCCG is talking to Dropbox and Dropbox is finding the file.

Dropbox is reporting back to LackeyCCG that the file is now located at the https:// location and then LackeyCCG reports a timeout to the GUI.

Code Select Expand

GET /u/7427384/LBPTCG/Maximum/updatelist.txt HTTP/1.1

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.15) Gecko/20080623 Firefox/2.0.0.15

Host: dl.dropboxusercontent.com

Accept: */*



HTTP/1.1 302 FOUND

cache-control: no-cache

Content-Type: text/html; charset=utf-8

Date: Wed, 16 Jul 2014 21:48:15 GMT

location: https://dl.dropboxusercontent.com/u/7427384/LBPTCG/Maximum/updatelist.txt

pragma: no-cache

Server: nginx

set-cookie: flash=; Domain=dropbox.com; expires=Wed, 16 Jul 2014 21:48:15 GMT; Path=/; httponly

set-cookie: bang=; Domain=dropbox.com; expires=Wed, 16 Jul 2014 21:48:15 GMT; Path=/; httponly

set-cookie: uc_session=IwaBFowg9PYTIL6BeE5mNWOqlhoLzbFRBM1rSfRu5YYp5A7pGpYiEFX6AHceayHG; Domain=dropboxusercontent.com; Path=/; secure; httponly

Content-Length: 410

Connection: keep-alive



<html>

  <head><title>Found</title></head>

  <body>

    <h1>Found</h1>

    <p>The resource was found at <a href="https://dl.dropboxusercontent.com/u/7427384/LBPTCG/Maximum/updatelist.txt">https://dl.dropboxusercontent.com/u/7427384/LBPTCG/Maximum/updatelist.txt</a>;

you should be redirected automatically.



<!--  --></p>

    <hr noshade>

    <div align="right">WSGI Server</div>

  </body>

</html>



When I try to point LackeyCCG to the https:// version of the updatelist I'm not seeing any traffic going out to Dropbox or really any TCP or HTTP traffic during the time I attempt to have LackeyCCG check the https:// URL for the updatelist. 

This could be another sign that I'm not running the version of the client that has https:// support patched in and the client is erroring out immediately upon seeing a non http:// URL.

LackeyCCG Windows -> Build Date: 07-13-14 is what is reported in the client but this is all that I see at the moment.  Are there any log files or similar data that I could get on this side that may help you get more information?

[Trevor]

I see that this does not work on windows and I'll fix it.