Is there an option in htmlunit to allow HTTP 302 to be treated as 303? I have a page where I POST to a resource, I receive a 302 back from the server, and then I do a GET on that new location. The output I'm getting is: main: Setting project property: webtest.version -> Canoo Webtest: R_1365.
BUILD FAILED C:\Documents and Settings\ccopeland\Desktop\canoo-webtest-1365\tests\CRUD-weblink.xml:16: Canoo Webtest: R_1365. Test failed. Test step clickButton (C:\Documents and Settings\ccopeland\Desktop\canoo-webtest-1365\tests\CRUD-weblink.xml:46: ) named "Click the Add button for Web Links" failed with message "Step[clickButton "Click the Add button for Web Links" (14/19)]: Script error loading page executing webtest at: clickButton Wrapped com.gargoylesoftware.htmlunit.FailingHttpStatusCodeException: 302 Moved Temporarily for http://172.16.34.41:8080/admin/webLink.do (http://172.16.34.41:8080/admin/scripts/common.js#667) Source code: function () { [native code, arity=0] } " at com.canoo.webtest.ant.WebtestTask.stopBuildIfNeeded(WebtestTask.java:186) at com.canoo.webtest.ant.WebtestTask.execute(WebtestTask.java:155) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275) at org.apache.tools.ant.Task.perform(Task.java:364) at org.apache.tools.ant.Target.execute(Target.java:341) at org.apache.tools.ant.Target.performTasks(Target.java:369) at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216) at org.apache.tools.ant.Project.executeTarget(Project.java:1185) at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:40) at org.apache.tools.ant.Project.executeTargets(Project.java:1068) at org.apache.tools.ant.Main.runBuild(Main.java:668) at org.apache.tools.ant.Main.startAnt(Main.java:187) at org.apache.tools.ant.launch.Launcher.run(Launcher.java:246) at org.apache.tools.ant.launch.Launcher.main(Launcher.java:67) I've looked around on the htmlunit site a bit and found: http://sourceforge.net/tracker/index.php?func=detail&aid=1439464&group_id=47038&atid=448266 but this seems to address proxy usage and not this particular issue. As a note, Section 10.3.3 of http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html states that most user agent implementations treat 302 as 303. Thanks! Craig __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com _______________________________________________ WebTest mailing list [email protected] http://lists.canoo.com/mailman/listinfo/webtest
