Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!news.albasani.net!news.musoftware.de!wum.musoftware.de!feeds.phibee-telecom.net!talisker.lacave.net!lacave.net!not-for-mail From: Martin Hansen Newsgroups: comp.lang.ruby Subject: Re: Digest::Base problem Date: Thu, 12 May 2011 08:57:19 -0500 Organization: Service de news de lacave.net Lines: 33 Message-ID: <519b405eae994c781e4eb36ef2b02b62@ruby-forum.com> References: <44e6eed427046cccdb19c01bb85b6906@ruby-forum.com> <5cd36eefaa33f21217f8d18ae36b82ba@ruby-forum.com> NNTP-Posting-Host: bristol.highgroove.com Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Trace: talisker.lacave.net 1305208815 63481 65.111.164.187 (12 May 2011 14:00:15 GMT) X-Complaints-To: abuse@lacave.net NNTP-Posting-Date: Thu, 12 May 2011 14:00:15 +0000 (UTC) In-Reply-To: X-Received-From: This message has been automatically forwarded from the ruby-talk mailing list by a gateway at comp.lang.ruby. If it is SPAM, it did not originate at comp.lang.ruby. Please report the original sender, and not us. Thanks! For more details about this gateway, please visit: http://blog.grayproductions.net/categories/the_gateway X-Mail-Count: 383069 X-Ml-Name: ruby-talk X-Rubymirror: Yes X-Ruby-Talk: <519b405eae994c781e4eb36ef2b02b62@ruby-forum.com> Xref: x330-a1.tempe.blueboxinc.net comp.lang.ruby:4363 >> Can we somehow test if Ruby has SSL support - without using digest - >> which appears to be broken? > > Sure. Try to access a website that uses HTTPS, like so: irb(main):001:0> require 'httpclient' ArgumentError: undefined class/module Digest::Base from :29:in `require' from :29:in `require' from /home/maasha/Install/src/Martin/lib/ruby/gems/1.9.1/gems/httpclient-2.2.0.2/lib/httpclient.rb:11:in `' from :33:in `require' from :33:in `rescue in require' from :29:in `require' from (irb):1 from ./irb:12:in `
' OK, so something ssl is probably fubar. It is strange that it appears to be a problem with both the precompiled debian packages and my ruby do-it-yourself compile. Grrr. I need some systematic approach to track down this issue. Martin -- Posted via http://www.ruby-forum.com/.