Browse: Home / / Adobe's *@(#*&$ Browser Requirements

Adobe's *@(#*&$ Browser Requirements

By barneyb on April 28, 2007

This chaps my @$$ every time I have to set up a new server.  Adobe's site simply blocks if you don't have a JS enabled browser.  I never install a GUI on my servers (why should I?), and every time I need to install CF, I'm stuck downloading it to my local machine, and then uploading back up to the server.  Repeat for each hotfix.  Aaaarrrggghhhh!

Posted in

8 responses to “Adobe's *@(#*&$ Browser Requirements”

  1. andy matthews
    andy matthews
    April 28, 2007 at 10:08 pm |

    Why not just browse to the link to the file, transfer the link to your server, then just download it normally from there?

  2. barneyb
    barneyb
    April 28, 2007 at 10:13 pm |

    You have to be logged in to download software. If you copy and paste a link between computers, you won't have a logged in session, so you'll get booted to the login form, which will then boot you to the requirements page. I suppose you could copy your cookies, but that's hardly straightforward with memory-only cookies.

  3. Erwin Verdonk
    Erwin Verdonk
    April 28, 2007 at 10:29 pm |

    Hi Barney,

    I think you havent tried hard enough ;-).

    Coldfusion Download (dont use the dropdown but scrolldown): http://www.adobe.com/downloads/?product_list=%2Fgo%2Ftrycoldfusion&Submit=Go
    Coldfusion Hotfixes: http://www.adobe.com/cfusion/knowledgebase/index.cfm?id=tn_17883

    It works for me here without JavaScript.

    Cheers,
    Erwin

  4. tony petruzzi
    tony petruzzi
    April 29, 2007 at 4:17 am |

    put a copy of the thing on a UNC share, a CD or a thumbdrive and stop your bitching already.

    ;)

  5. Cozmo
    Cozmo
    April 29, 2007 at 6:32 am |

    Potential solution:

    I wrote a CF script a while back that would log me into the dynDNS.org site and create dns Records. I don't have the code lying around or I would post it. Basically I used the cfhttp and cfhttpparam type = "Cookie" to maintain the session.

    As far as JS enabled you might want to try spoofing the browser like so.

    cfhttp useragent="some JS enabled browser"

    I would do it on CF for POC and then port it to PHP or Python if it works.

  6. barneyb
    barneyb
    April 30, 2007 at 8:07 am |

    Erwin,

    Those links all bring you to the login form when you click them. Perhaps you had already logged in?

    Tony,

    If I had physical access to the server, I'd just use the installation CDs.

  7. Sean Corfield
    Sean Corfield
    May 2, 2007 at 9:36 pm |

    Why would you download the files every time you get a new server? Surely you keep the downloaded files all in a shared storage area somewhere and then you'd just copy the files onto the new server?

    In fact we actually kept the CF installer and hotfixes under SVN so that we can manage the configuration of our servers more easily.

  8. barneyb
    barneyb
    May 2, 2007 at 10:41 pm |

    Sean,

    When I was managing "real" infrastructure, I did much the same thing. But now that it's just my personal machines, I don't anymore. That's due in no small part to the fact that Comcast (my ISP) throttles outgoing traffic to about 40k (yes, slower than a modem) beyond a certain point, which makes uploading a 300MB file take forever. As such, any sort of cache I'd have locally wouldn't be of any use unless the new machine was also local (which wasn't the case). So I used my office workstation (via rdesktop) to download and reupload it.