Forum: Ruby open-uri can read slashdot rss, but not digg rss ?

Announcement (2017-05-07): is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see and for other Rails- und Ruby-related community platforms.
Aec10c73877ea116bab759e060b2fcb3?d=identicon&s=25 (Guest)
on 2007-03-18 21:31
(Received via mailing list)
Here's an irb session, this used to work, maybe something new about
digg's rss feed ?

irb(main):001:0> require 'open-uri'
=> true
irb(main):002:0> open('
=> 263
irb(main):003:0> open('
/usr/lib/ruby/1.8/timeout.rb:54:in `rbuf_fill': execution expired
        from /usr/lib/ruby/1.8/timeout.rb:56:in `timeout'
        from /usr/lib/ruby/1.8/timeout.rb:76:in `timeout'
        from /usr/lib/ruby/1.8/net/protocol.rb:132:in `rbuf_fill'
        from /usr/lib/ruby/1.8/net/protocol.rb:116:in `readuntil'
        from /usr/lib/ruby/1.8/net/protocol.rb:126:in `readline'
        from /usr/lib/ruby/1.8/net/http.rb:1988:in `read_status_line'
        from /usr/lib/ruby/1.8/net/http.rb:1977:in `read_new'
        from /usr/lib/ruby/1.8/net/http.rb:1046:in `request'
         ... 8 levels...
        from /usr/lib/ruby/1.8/open-uri.rb:86:in `open'
        from (irb):3:in `irb_binding'
        from /usr/lib/ruby/1.8/irb/workspace.rb:52:in `irb_binding'
        from /usr/lib/ruby/1.8/irb/workspace.rb:52

happens every time !
Aec10c73877ea116bab759e060b2fcb3?d=identicon&s=25 (Guest)
on 2007-03-18 21:51
(Received via mailing list)
On Mar 18, 3:28 pm, "" <> wrote:
> /usr/lib/ruby/1.8/timeout.rb:54:in `rbuf_fill': execution expired
>         from /usr/lib/ruby/1.8/open-uri.rb:86:in `open'
>         from (irb):3:in `irb_binding'
>         from /usr/lib/ruby/1.8/irb/workspace.rb:52:in `irb_binding'
>         from /usr/lib/ruby/1.8/irb/workspace.rb:52
> happens every time !

Digg wants a specific user-agent, like the one my FF uses.  Why in the
world would they do that ?  What/who are they hoping to prevent.  Do
they really only want browsers connecting to there feeds ?
1c0cd550766a3ee3e4a9c495926e4603?d=identicon&s=25 John Joyce (Guest)
on 2007-03-19 15:44
(Received via mailing list)
They may just be keeping track of what user-agents are being used.
Though browser sniffing is almost pointless.
Should be easy enough to give it whatever string you like. "user-
agent" is nothing but a string anyway, almost meaningless, because it
isn't guaranteed to be true or mean anything valid or verifiable.
(like microsoft's early corruption of it, to circumvent browser
sniffing and blocking by starting it's MSIE user-agent string with
Mozilla 4.x (compatible... ))
This topic is locked and can not be replied to.