Sha256: a38050fccd82881e8b7895036f691b3760c59a305f7f1cdf018799ffff6a5b88

Contents?: true

Size: 531 Bytes

Versions: 8

Compression:

Stored size: 531 Bytes

Contents

Q:: Why do I keep getting an EOFError?

A:: For older versions of mechanize turning off keep_alive could help with the
    problem, but mechanize now has more robust handling of persistent
    connections.

    Older versions of mechanize would raise an EOFError when a chunked body was
    not terminated properly, a common bug of IIS servers.  Since 2.0
    Mechanize::ResponseReadError is raised containing the original response and
    body read so far so if the server is broken you can still retrieve the
    entire content.

Version data entries

8 entries across 8 versions & 4 rubygems

Version Path
domo-0.0.5 vendor/bundle/ruby/1.9.1/gems/mechanize-2.1/FAQ.rdoc
diamond-mechanize-2.4 FAQ.rdoc
diamond-mechanize-2.3 FAQ.rdoc
diamond-mechanize-2.2 FAQ.rdoc
diamond-mechanize-2.1 FAQ.rdoc
mechanize-2.1 FAQ.rdoc
mechanize-2.1.pre.1 FAQ.rdoc
aai10-mechanize-2.0.1.0 FAQ.rdoc