[Mono-bugs] [Bug 59794][Maj] Changed - problems with cookieless sessions and databinding

[bugzilla-daemon@bugzilla.ximian.com]

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by chris@turchin.net.

http://bugzilla.ximian.com/show_bug.cgi?id=59794

--- shadow/59794	2004-06-09 02:13:04.000000000 -0400
+++ shadow/59794.tmp.5016	2004-06-09 15:46:31.000000000 -0400
@@ -107,6 +107,49 @@
 go.img =  "images/folder.gif";
 go.url = "default.aspx?dir="+HttpUtility.UrlEncode(go.Path);
 
 so don't expect them to contain the cookieless session stuff.
 
 
+
+------- Additional Comments From chris@turchin.net  2004-06-09 15:46 -------
+There is still an inconsistency in xsp, even if I described it
+incorrectly in my bugreport:
+
+i am binding these paths:
+
+go.img =  "thumbnail.ashx?fmt=Thumb&img="+HttpUtility.UrlEncode(go.Path);
+go.url = "preview.aspx?img="+HttpUtility.UrlEncode(go.Path);
+
+and i expected that the session string appears in the path, but that
+is not what should happen at all. instead, xsp/mod_mono should stop
+(incorrectly) prepending the complete path to the file in this case,
+regardless of the session string:
+
+results on MS.NET for databinding of this nature:
+	
+<a id="mediaList__ctl0_galleryObjectLink"
+href="preview.aspx?img=c%3a%5ctemp%5cADZBatchMediaQueryInterface.jpg"><img
+src="thumbnail.ashx?fmt=Thumb&amp;img=c%3a%5ctemp%5cADZBatchMediaQueryInterface.jpg"
+border="0" /></a>
+<asp:literal id="galleryObjectName">
+ADZBatchMediaQueryInterface.jpg
+</asp:literal>
+</td>
+
+note the path without "/gd-gallery/" --- results on mod_mono/xsp:
+
+<td>
+<a id="mediaList__ctrl0a_galleryObjectLink"
+href="/gd-gallery/preview.aspx?img=%2fdata%2fimages%2fhw.jpg"><img
+src="/gd-gallery/thumbnail.ashx?fmt=Thumb&amp;img=%2fdata%2fimages%2fhw.jpg"
+border="0" />
+</img></a>
+<asp:literal id="galleryObjectName">
+hw.jpg
+</asp:literal>
+
+since the relative path in ms.net is still relative to a path
+INCLUDING the session key (which just looks like a folder to the
+browser) it will be requested from the server as such. in mono, the
+complete (and wrong) path to the file shows up, and the request fails.
+