Hi john.That's expected -- this affects the parsing of the HTML. It does not
Thanks for your reply. I tried your suggestion of using RobustFactory, and
still get a badly maligned html back!!! The html is listed below. I would
modify the HTML.
have thought that the mech process, would have interpreted theYes, only the head element is read (albeit with a slightly fuzzy
"http-equiv="refresh" Unfortunately, mechanize apparently isn't able to
handle a "<meta http-equiv="refresh" url="/foo/..."when it's inside the
<bodyof the html...
definition of "head element").
In a theoretical future unstable branch, that might change, but currently
mechanize doesn't try all that hard to work well with bad HTML.
Currently, you have to work around this kind of issue. You can perform
the refresh manually, or modify the HTML and call .set_response(), or
replace the HTTPEquivProcessor with your own (you could use
HTTPEquivProcessor itself -- you can pass a parser factory function to its
constructor).
John