What's the RIGHT way to accomplish controlling the source IP and port with Mechanize? #597

astounding · 2022-05-12T01:38:06Z

astounding
May 12, 2022

I didn't see anything obvious in documentation showing how to control the SOURCE IP and PORT that Mechanize binds to. I know Net::HTTP has #local_port and #local_host methods to set and control source IP and PORT binding, but I don't know how to tell my Mechanize agent to set those. Instead I resorted to this UGLY kludge:

... ruby script body ...

BIND_IP = '192.168.55.121'  ## Totally bogus IP for example purposes

## ===============
## START OF KLUDGE
## ===============
## KLUDGE work-around for Mechanize NOT supporting binding to source IP
## and port:
##
## Rewrite Net::HTTP::Persistent::Connection#initialize() from
## /usr/local/lib/ruby/gems/2.7/gems/net-http-persistent-4.0.1/lib/net/http/persistent/connection.rb
## to set the local host and port we want to bind to for the connection.
## There has GOT to be a way to pass these options in legitimately
## instead of using a kludge like this.  An elegant, right way to do it.
class Net::HTTP::Persistent::Connection
  def initialize http_class, http_args, ssl_generation
    @http           = http_class.new(*http_args)
    @ssl_generation = ssl_generation

    ## SOURCE IP we want to bind to
    @http.local_host = BIND_IP
    @http.local_port = 0

    reset
  end
end
## =============
## END OF KLUDGE
## =============

... ruby script body that uses Mechanize ...

Is there a way to pass parameters or options to Mechanize either upon agent creation OR when executing the agent's #get or #post methods so that it sets @http.local_host instead of me having to resort to using this nasty kludge just to force the TCP HTTP socket to bind to the local IP I choose for the outgoing client connection(s)?

Thanks in advance for any pointers/tips/suggestions!

--Aaron out.

flavorjones · 2022-05-20T21:28:14Z

flavorjones
May 20, 2022
Maintainer

Hi @astounding, thanks for asking this question.

As you have already discovered, Mechanize wraps Net::HTTP::Persistent which is itself a wrapper around Net::HTTP. However, Net::HTTP::Persistent doesn't expose the exact same API as Net::HTTP and so some attributes (like #local_host) are settable on an instance of Net::HTTP but not Net::HTTP::Persistent.

I'd like to suggest that you could either ask about this or send a pull request to https://github.com/drbrain/net-http-persistent. Once NHP has exposed them, then we can likewise expose them in Mechanize. If you want to create a PR my suggestion would be to follow the pattern provided by the #open_timeout attribute.

I hope this response was helpful! Let me know if you have any more questions, I'm happy to provide mentorship or review a PR to Mechanize and/or NHP!

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

What's the RIGHT way to accomplish controlling the source IP and port with Mechanize? #597

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{editor}}'s edit

{{editor}}'s edit

Uh oh!

Replies: 1 comment

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{editor}}'s edit

{{editor}}'s edit

Uh oh!

Select a reply

Uh oh!

What's the RIGHT way to accomplish controlling the source IP and port with Mechanize? #597

Uh oh!

Uh oh!

astounding May 12, 2022

Replies: 1 comment

Uh oh!

Uh oh!

flavorjones May 20, 2022 Maintainer

astounding
May 12, 2022

flavorjones
May 20, 2022
Maintainer