Hello! I was wondering if there is a reason why relative action attributes are not allowed in html:form tags. In the code, request.getContextPath() gets appended unconditionally to all action attributes. In my situation, the ContextPath is not the same as the location of my pages, because we use ProxyPass statements in Apache config file, and <html:form> ends up generating a <form> tag with incorrect action attribute. I wish it would simply pass the relative action through, optionally appending sessionid, etc., but not adding any prefixes to the resulting action. A workaround was found where I use regular <form> tag instead of html:form, and in each of the contained elements (html:selects, html:texts, etc.) I have to add a name="myForm" attribute, so that they know where to find their values. In addition, this will not work in a situation with disabled cookies, since I don't append any session id to the form action (I guess I could do it with a scriptlet). Overall, not a very clean workaround. So, do you think that org.apache.struts.taglib.html.FormTag should be modified to allow for relative action targets? Perhaps, anything that doesn't start with a "/" should be considered relative and simply passed through? Alternatively, an additional attribute could be added to html:form tag to turn URL processing on or off. Or am I missing something in the overall logic, and perhaps there's a good reason not to allow that? I'd appreciate any comments.
Thanks! -M- -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
