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.

rack-openid with fcgi -- problems

#4359

My app works fine with mongrel, but fails with fcgi. Unfortunately, I am on a shared host (bluehost), so I can't switch.

I am not sure whether this is a Lockdown or a Rack OpenID problem.

The same app running on two different handlers produces different results:

Two logs of the same app:

Running on Mongrel:

Processing UserSessionsController#new (for 192.168.10.101 at 2010-04-06 01:08:53) [GET]
  Parameters: {"action"=>"new", "controller"=>"user_sessions"}
Rendering template within layouts/application
Rendering user_sessions/new
Completed in 1017ms (View: 227, DB: 24) | 200 OK [http://192.168.10.104/user_session/new]

Processing UserSessionsController#create (for 192.168.10.101 at 2010-04-06 01:08:57) [POST]
  Parameters: {"user_session"=>{"remember_me"=>"true"}, "method"=>:get, "authenticity_token"=>"mqNJ5GqZlXAWI7yNxFoNrlYMmk6wjLcfA+FPO2+hfPE=", "action"=>"create", "openid_identifier"=>"https://www.google.com/accounts/o8/id", "controller"=>"user_sessions"}
Completed in 662ms (View: 4, DB: 23) | 401 Unauthorized [http://192.168.10.104/user_session]
WARNING: making https request to https://www.google.com/accounts/o8/id without verifying server certificate; no CA path was specified.
WARNING: making https request to https://www.google.com/accounts/o8/ud without verifying server certificate; no CA path was specified.
Generated checkid_setup request to https://www.google.com/accounts/o8/ud with assocication <filtered>

Error attempting to use stored discovery information: OpenID::TypeURIMismatch
Attempting discovery to verify endpoint
Performing discovery on https://www.google.com/accounts/o8/id?id=<filtered>
WARNING: making https request to https://www.google.com/accounts/o8/id?id=<filtered> without verifying server certificate; no CA path was specified.
Using 'check_authentication' with https://www.google.com/accounts/o8/ud
WARNING: making https request to https://www.google.com/accounts/o8/ud without verifying server certificate; no CA path was specified.

Processing UserSessionsController#create (for 192.168.10.101 at 2010-04-06 01:09:05) [POST]
  Parameters: {"remember_me"=>"true", "method"=>:get, "action"=>"create", "for_session"=>"1", "controller"=>"user_sessions", "locale"=>"en"}
...

Runnning on FCGI:

Processing UserSessionsController#new (for 79.151.153.101 at 2010-04-09 21:09:21) [GET]
  Parameters: {"action"=>"new", "controller"=>"user_sessions"}
Rendering template within layouts/application
Rendering user_sessions/new
Completed in 17ms (View: 16, DB: 0) | 200 OK [http://dev.irequestlive.com/user_session/new]


Processing UserSessionsController#create (for 79.151.153.101 at 2010-04-09 21:09:24) [POST]
  Parameters: {"user_session"=>{"remember_me"=>"true"}, "authenticity_token"=>"sub6pvUyQ3mZl2eqc7HUD1yxoNz6sBH7RdkstoShPY4=", "action"=>"create", "openid_identifier"=>"https://www.google.com/accounts/o8/id", "controller"=>"user_sessions"}
Completed in 5ms (View: 0, DB: 0) | 401 Unauthorized [http://dev.irequestlive.com/user_session]
WARNING: making https request to https://www.google.com/accounts/o8/id without verifying server certificate; no CA path was specified.
WARNING: making https request to https://www.google.com/accounts/o8/ud without verifying server certificate; no CA path was specified.
Generated checkid_setup request to https://www.google.com/accounts/o8/ud with assocication <filtered>


Processing HomeController#index (for 79.151.153.101 at 2010-04-09 21:09:26) [POST]
...

Reported by glebm · April 10th, 2010 @ 04:40 AM

State: stale
Milestone: none
Assigned to: nobody
Importance: none

Activity

  1. Santiago Pastorino
    Santiago Pastorino
    • State changed from new to open

    This issue has been automatically marked as stale because it has not been commented on for at least three months.

    The resources of the Rails core team are limited, and so we are asking for your help. If you can still reproduce this error on the 3-0-stable branch or on master, please reply with all of the information you have about it and add "[state:open]" to your comment. This will reopen the ticket for review. Likewise, if you feel that this is a very important feature for Rails to include, please reply with your explanation so we can consider it.

    Thank you for all your contributions, and we hope you will understand this step to focus our efforts where they are most helpful.

    February 2nd, 2011 @ 04:51 PM

  2. Santiago Pastorino
    Santiago Pastorino
    • State changed from open to stale

    February 2nd, 2011 @ 04:51 PM

  3. bingbing