Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 6238333
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 24, 20262026-05-24T11:11:34+00:00 2026-05-24T11:11:34+00:00

Ruby’s OpenURI provides a content_length_proc option which allows determining* content length before the actual

  • 0

Ruby’s OpenURI provides a content_length_proc option which allows determining* content length before the actual transfer is started:

open(url, :content_length_proc => lambda { |content_length|
  puts "Content Length: #{content_length}"
}) { |data|
   # data.meta, data.read etc.
}

Is there a way for this proc to abort the actual, full retrieval?

* I’m aware this is not reliable – but it’s sufficient for a simple heuristic in my case

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-24T11:11:35+00:00Added an answer on May 24, 2026 at 11:11 am

    This is the corresponding code from open-uri.rb:

    if options[:content_length_proc] && Net::HTTPSuccess === resp
      if resp.key?('Content-Length')
        options[:content_length_proc].call(resp['Content-Length'].to_i)
      else
        options[:content_length_proc].call(nil)
      end
    end
    resp.read_body {|str|
      ...
    }
    

    So as you can see the return value of content_length_proc is ignored. But, what you could simply do to cancel the operation is raise some form of error in the callback – this will effectively abort further execution. If you raise a dedicated error class you could even rescue it and react to that specific situation:

    begin
      open(url, :content_length_proc => lambda { |content_length|
        puts "Content Length: #{content_length}"
      }) { |data|
        # data.meta, data.read etc.
      }
    rescue MyError
      # react to it
    end
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

Ruby looks a very cool language. I've started learning it for the past two
Ruby has this very interesting functionality in which when you create a class with
ruby has some edge cases which is hard to explain because parsing brings some
Ruby, which is normally very forgiving, is giving me an error on a while
Ruby's Enumerable has a select which can select certain items from an array: parent=@sections.select
Ruby is a beatifull language, but with a key word end which I hates
Ruby Version Manager allows us to use an .rvmrc file in each project to
Ruby has two different exceptions mechanisms: Throw/Catch and Raise/Rescue. Why do we have two?
Ruby setters—whether created by (c)attr_accessor or manually—seem to be the only methods that need
Ruby's standard popen3 module does not work on Windows. Is there a maintained replacement

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.