/usr/lib/ruby/1.8/net/protocol.rb:135:in `sysread': Connection reset by
peer (Errno::ECONNRESET)
from /usr/lib/ruby/1.8/net/protocol.rb:135:in `rbuf_fill'
from /usr/lib/ruby/1.8/timeout.rb:62:in `timeout'
from /usr/lib/ruby/1.8/timeout.rb:93:in `timeout'
from /usr/lib/ruby/1.8/net/protocol.rb:134: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:2020:in `read_status_line'
from /usr/lib/ruby/1.8/net/http.rb:2009:in `read_new'
from /usr/lib/ruby/1.8/net/http.rb:1050:in `request'
from ./rssModule.rb:40:in `extractor'
from /usr/lib/ruby/1.8/net/http.rb:543:in `start'
from ./rssModule.rb:38:in `extractor'
from ./rssModule.rb:19:in `each'
from ./rssModule.rb:19:in `extractor'
from rss.rb:38
I don't know exactly about the problem ie. whether it is OS dependent or
browser dependent etc.. My code snippet is shown below :
uri =
URI.parse("Control API access with domain-wide delegation - Google Workspace Admin Help)
header = { "User-Agent"=>"Mozilla/4.0 (compatible; MSIE 5.5; Windows NT
5.0)" }
http = Net::HTTP.new(uri.host, uri.port)
http.use_ssl()
http.start do |https|
request = Net::HTTP::Get.new(uri.path,
header)
response = https.request(request,
header)
response.value
end
Please help me. I'm in big trouble if I can't solve it.
First, the URL is badly encoded, in the end of the string:
http%3A%2%2Fwww...."
should be
http%3A%2F%2Fwww...."
Second, to access a protected resource, it's not enought just to start
a URL with https
You need to know the login & password, once you know them you can
should set them before performing a request:
request.basic_auth 'account', 'password'
Dmitry
Hi,
Thanks for the reply. I applied basic authentication and changed the
url but still it is showing the same error. Besides can you please tell
me is this error generated only for those sites which require basic
authentication or this error can be generated for other sites which
doesnot require any type of authentication at all. I'll be pleased to
hear from you.
The error will be generated anytime when the server doesn't want to
talk to you, eg. because of auth failure or service outage.
And about basic auth, actually it's only one of the many ways to
authenticate on the web, and I'm sure that Google Account protected
services support it. Probably the only way to fullfil such request is
to emulate a browser request and store all cookies & headers the
google will set. But it won't be easy, if possible at all. So you'll
better find an API way to access the service, either don't scrap such
URLs. And also I'm quite sure that it violates Google Terms.
1. No, I don't think that the timeout is a problem there.
2. As I said, I think that there are no easy way or no way at all to
do it without using google apis.
