DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26192>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26192 forward element redirect and className attributes not honored [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|WORKSFORME | ------- Additional Comments From [EMAIL PROTECTED] 2004-01-23 12:20 ------- Thanks for the test case. Unfortunately it wasn't easy to fire them up, as the class org.apache.struts.webapp.exercise.SuccessAction you have put into struts-config.xml: <action path="/forward-redirect-default" type="org.apache.struts.webapp.exercise.SuccessAction" > <forward name="success" path="/" redirect="true" contextRelative="true" /> </action> <action path="/forward-redirect-default-module" type="org.apache.struts.webapp.exercise.SuccessAction" > <forward name="success" path="/" redirect="true" /> </action> <action path="/forward-redirect-path" type="org.apache.struts.webapp.exercise.SuccessAction" > <forward name="success" path="/html-link.do" redirect="true" /> </action> does not exist in the package org.apache.struts.webapp.exercise. this I have used org.apache.struts.scaffold.SuccessAction instead (I guess it was ment to be the same). this makes me wonder though if you yourself have run these examples. Unfortunately the examples you provided are underlinging the bug I found. neither of the three actions with redirect="true" do an actual HTTP redirect. testing with wget, as earlier: $ wget http://localhost:8080/struts-examples/exercise/forward-redirect-default.do --13:17:39-- http://localhost:8080/struts-examples/exercise/forward-redirect-default.do => `forward-redirect-default.do' Resolving localhost... done. Connecting to localhost[127.0.0.1]:8080... connected. HTTP request sent, awaiting response... 200 OK Length: 0 [text/html] [ <=> ] 0 --.--K/s 13:17:39 (0.00 B/s) - `forward-redirect-default.do' saved [0/0] $ wget http://localhost:8080/struts-examples/exercise/forward-redirect-default-module.do --13:17:59-- http://localhost:8080/struts-examples/exercise/forward-redirect-default-module.do => `forward-redirect-default-module.do' Resolving localhost... done. Connecting to localhost[127.0.0.1]:8080... connected. HTTP request sent, awaiting response... 200 OK Length: 0 [text/html] [ <=> ] 0 --.--K/s 13:17:59 (0.00 B/s) - `forward-redirect-default-module.do' saved [0/0] $ wget http://localhost:8080/struts-examples/exercise/forward-redirect-path.do --13:18:15-- http://localhost:8080/struts-examples/exercise/forward-redirect-path.do => `forward-redirect-path.do' Resolving localhost... done. Connecting to localhost[127.0.0.1]:8080... connected. HTTP request sent, awaiting response... 200 OK Length: 0 [text/html] [ <=> ] 0 --.--K/s 13:18:15 (0.00 B/s) - `forward-redirect-path.do' saved [0/0] in none of the cases does the action send back a 302 Moved Temorarily response with the appropriate Location header, which would be the proper behaviour. one more note: would you mind not marking the bug as resolved until it really is. thanks. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
