DynamicURI encodes the names and values added as path info and query data.
I was talking with Leon Atkinson and he said this is wrong wrt sending an
url in an anchor tags href attribute. It is up to the browser to perform
the encoding. It is rather harmless as links appear to work either way, but
I was wondering if there was a reason (use of DynamicURI) where the encoding
is appropriate?
Some examples:
<a href="http://host/servlets/Turbine/template/,index.html">
<a href="http://host/servlets/Turbine/template/%2Cindex.html">
both lead Turbine's parameterParser to assign template=,index.html
<a href="http://host/servlets/Turbine/template/%2Findex.html"> will lead to
bad behavior by Apache. I am starting to not see this as necessarily a bug.
As Apache is probably seeing all the
/ as converted by the browser to %2F and so the path appears wrong.
One thing I haven't figured out is why in
<a href="http://host/servlets/Turbine/template/%2Cindex.html">
the % is not converted to %25 (I assume it should be, by the browser), so
that %252C would come through Apache as %2C and not "," as it is.
Something strange is going on. What if I want
<a href="http://host/servlets/Turbine/template/%2Cindex.html">
to mean template=%2Cindex.html and not template=,index.html.
Hell, this is getting confusing, but what is the answer to my orginal
question? What was my original question? :) Oh yeah, why is DynamicURI url
encoding parameter data when it appears unnecessary?
John McNally
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
