Lighthouse has a new layout. Prefer the old one? Return to the old layout, and switch back any time from the link at the top of each page.

This project is archived and is in readonly mode.

Use HTTPS in Github URLs

#6162

Since Github changed their default protocol to https I'm getting a redirection forbidden error when trying to run:

 $ rails generate jquery:install --ui
       remove  public/javascripts/controls.js
       remove  public/javascripts/dragdrop.js
       remove  public/javascripts/effects.js
       remove  public/javascripts/prototype.js
     fetching  jQuery (1.4.3)
       create  public/javascripts/jquery.js
       create  public/javascripts/jquery.min.js
     fetching  jQuery UI (latest 1.x release)
       create  public/javascripts/jquery-ui.js
       create  public/javascripts/jquery-ui.min.js
     fetching  jQuery UJS adapter (github HEAD)
 /usr/local/lib/ruby/1.8/open-uri.rb:174:in `open_loop': redirection forbidden: http://github.com/rails/jquery-ujs/raw/master/src/rails.js -> https://github.com/rails/jquery-ujs/raw/master/src/rails.js (RuntimeError)

Reported by Federico Builes · December 14th, 2010 @ 08:47 AM

State: invalid
Milestone: none
Assigned to: nobody
Importance: Low

Activity

  1. Federico Builes
    Federico Builes
    • Tag changed from railties to patch, railties

    A patch at https://gist.github.com/raw/740159/de70d19ac4c00a051b7005abd7d0b4a7... fixes this issue. Lighthouse's not allowing my Chrome to upload files (to the initial report or in the comments).

    December 14th, 2010 @ 08:51 AM

  2. Piotr Sarnacki
    Piotr Sarnacki
    • Importance changed from to Low

    Are you sure that you fixed the right thing? The update is in the railties/Rakefile, which should have nothing to do with generators. Also, the error that you get from rake g jquery:install is from ruby (open-uri) and update_ujs uses curl (and works perfectly, try cloning rails and run rake update_ujs)

    Is that task a part of rails? If it's coming from a gem, you should check the implementation of that particular gem.

    December 14th, 2010 @ 09:54 AM

  3. Federico Builes
    Federico Builes

    You're totally right Piotr, that patch was retarded and should be ignored. A quick grep led me to think it was that but after reading the project's Gemfile I realize there's actually a jquery-rails gem that is the actual problematic gem.
    Thanks for the pointers and please close this as invalid.

    December 14th, 2010 @ 10:02 AM

  4. Piotr Sarnacki
    Piotr Sarnacki
    • State changed from new to invalid

    December 14th, 2010 @ 10:08 AM