Something is going wrong in our testing environment between mod_gzip (apache 1.3) and WWW::Mechanize;

posting a form to a relative URL like this: "../../file" is resulting in apache 404s; "dir1/file" is looked for instead of "dir1/dir2/file". It looks like the relative path is getting borked.

We're getting around it by disabling gzip in Mechanize but we'd prefer a more rigorous solution. Anyone have any suggestions?

Frankly, we're baffled and have not been able to even imagine a connection between the content encoding and a messed up filepath in the request...