Re: [T5] How to get ampersand () rendered raw / not encoded as amp;?
Martin, I'm guessing your mail client converted Josh's message because it rendered the in the url as amp; - just as you have explained and shown. As he said, url's with amp; in place of are actually correct and should not cause problems (I personally have never seen these urls cause any). chris Martin Grotzke wrote: On Mon, 2008-03-17 at 15:24 -0700, Josh Canfield wrote: If I am understanding you correctly, you are getting something like this in your source: iframe src=http://host/page?arg1=val1arg2=val2;/iframe Nope, unfortunately I get src=http://host/page?arg1=val1amp;arg2=val2; so the is rendered as amp; Cheers, Martin That is actually the correct behavior and it shouldn't be causing a problem in your browser. Are you seeing a problem? http://htmlhelp.com/tools/validator/problems.html#amp Josh On Mon, Mar 17, 2008 at 1:18 PM, Martin Grotzke [EMAIL PROTECTED] wrote: Hi, I have a an html element (iframe) that get's a property of my page class (the current query string) appended to its src attribute. The query string may contain the char, which always gets expanded as amp;. Is there any possibility to prevent T5 from encoding this char? Thanx cheers, Martin
Re: [T5] How to get ampersand () rendered raw / not encoded as amp;?
Hi, On Tue, 2008-03-18 at 14:19 +0100, Chris Lewis wrote: Martin, I'm guessing your mail client converted Josh's message because it rendered the in the url as amp; - just as you have explained and shown. Ok, thanx :) As he said, url's with amp; in place of are actually correct and should not cause problems (I personally have never seen these urls cause any). I would say that a request parameter appended with amp;param=value would be seen by the server as amp;param instead of just param. Cheers, Martin chris Martin Grotzke wrote: On Mon, 2008-03-17 at 15:24 -0700, Josh Canfield wrote: If I am understanding you correctly, you are getting something like this in your source: iframe src=http://host/page?arg1=val1arg2=val2;/iframe Nope, unfortunately I get src=http://host/page?arg1=val1arg2=val2; so the is rendered as amp; Cheers, Martin That is actually the correct behavior and it shouldn't be causing a problem in your browser. Are you seeing a problem? http://htmlhelp.com/tools/validator/problems.html#amp Josh On Mon, Mar 17, 2008 at 1:18 PM, Martin Grotzke [EMAIL PROTECTED] wrote: Hi, I have a an html element (iframe) that get's a property of my page class (the current query string) appended to its src attribute. The query string may contain the char, which always gets expanded as amp;. Is there any possibility to prevent T5 from encoding this char? Thanx cheers, Martin signature.asc Description: This is a digitally signed message part
Re: [T5] How to get ampersand () rendered raw / not encoded as amp;?
Hi, On 2008-03-18 15:41, Martin Grotzke wrote: Hi, On Tue, 2008-03-18 at 14:19 +0100, Chris Lewis wrote: Martin, I'm guessing your mail client converted Josh's message because it rendered the in the url as amp; - just as you have explained and shown. Ok, thanx :) As he said, url's with amp; in place of are actually correct and should not cause problems (I personally have never seen these urls cause any). I would say that a request parameter appended with amp;param=value would be seen by the server as amp;param instead of just param. W3C says otherwise: With HTML, the browser translates amp; to so the Web server would only see and not amp; in the query string of the request. http://htmlhelp.com/tools/validator/problems.html#amp It's not a problem. I see the exact same behaviour and it's working just fine. :) -Filip Cheers, Martin chris Martin Grotzke wrote: On Mon, 2008-03-17 at 15:24 -0700, Josh Canfield wrote: If I am understanding you correctly, you are getting something like this in your source: iframe src=http://host/page?arg1=val1arg2=val2;/iframe Nope, unfortunately I get src=http://host/page?arg1=val1arg2=val2; so the is rendered as amp; Cheers, Martin That is actually the correct behavior and it shouldn't be causing a problem in your browser. Are you seeing a problem? http://htmlhelp.com/tools/validator/problems.html#amp Josh On Mon, Mar 17, 2008 at 1:18 PM, Martin Grotzke [EMAIL PROTECTED] wrote: Hi, I have a an html element (iframe) that get's a property of my page class (the current query string) appended to its src attribute. The query string may contain the char, which always gets expanded as amp;. Is there any possibility to prevent T5 from encoding this char? Thanx cheers, Martin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [T5] How to get ampersand () rendered raw / not encoded as amp;?
Hi Martin, I'm confused by your statement: I would say that a request parameter appended with amp;param=value would be seen by the server as amp;param instead of just param. Does this mean that you are seeing a problem on the server side? What you are describing is not what I would expect, if you are seeing this then there might be something else going on. Josh On Tue, Mar 18, 2008 at 7:41 AM, Martin Grotzke [EMAIL PROTECTED] wrote: Hi, On Tue, 2008-03-18 at 14:19 +0100, Chris Lewis wrote: Martin, I'm guessing your mail client converted Josh's message because it rendered the in the url as amp; - just as you have explained and shown. Ok, thanx :) As he said, url's with amp; in place of are actually correct and should not cause problems (I personally have never seen these urls cause any). I would say that a request parameter appended with amp;param=value would be seen by the server as amp;param instead of just param. Cheers, Martin chris Martin Grotzke wrote: On Mon, 2008-03-17 at 15:24 -0700, Josh Canfield wrote: If I am understanding you correctly, you are getting something like this in your source: iframe src=http://host/page?arg1=val1arg2=val2;/iframe Nope, unfortunately I get src=http://host/page?arg1=val1arg2=val2; so the is rendered as amp; Cheers, Martin That is actually the correct behavior and it shouldn't be causing a problem in your browser. Are you seeing a problem? http://htmlhelp.com/tools/validator/problems.html#amp Josh On Mon, Mar 17, 2008 at 1:18 PM, Martin Grotzke [EMAIL PROTECTED] wrote: Hi, I have a an html element (iframe) that get's a property of my page class (the current query string) appended to its src attribute. The query string may contain the char, which always gets expanded as amp;. Is there any possibility to prevent T5 from encoding this char? Thanx cheers, Martin -- -- TheDailyTube.com. Sign up and get the best new videos on the internet delivered fresh to your inbox. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AW: [T5] How to get ampersand () rendered raw / not encoded as amp;?
Hi Martin, how is the query string is appended? There is always a difference in writing text and html. If you write text everything gets converted. If you write html (raw) everything will work. Please just post the tml-part in question. Maybe we can give a shorty for it. Cheers, Martin (Kersten) -Ursprüngliche Nachricht- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im Auftrag von Josh Canfield Gesendet: Dienstag, 18. März 2008 18:06 An: Tapestry users Betreff: Re: [T5] How to get ampersand () rendered raw / not encoded as amp;? Hi Martin, I'm confused by your statement: I would say that a request parameter appended with amp;param=value would be seen by the server as amp;param instead of just param. Does this mean that you are seeing a problem on the server side? What you are describing is not what I would expect, if you are seeing this then there might be something else going on. Josh On Tue, Mar 18, 2008 at 7:41 AM, Martin Grotzke [EMAIL PROTECTED] wrote: Hi, On Tue, 2008-03-18 at 14:19 +0100, Chris Lewis wrote: Martin, I'm guessing your mail client converted Josh's message because it rendered the in the url as amp; - just as you have explained and shown. Ok, thanx :) As he said, url's with amp; in place of are actually correct and should not cause problems (I personally have never seen these urls cause any). I would say that a request parameter appended with amp;param=value would be seen by the server as amp;param instead of just param. Cheers, Martin chris Martin Grotzke wrote: On Mon, 2008-03-17 at 15:24 -0700, Josh Canfield wrote: If I am understanding you correctly, you are getting something like this in your source: iframe src=http://host/page?arg1=val1arg2=val2;/iframe Nope, unfortunately I get src=http://host/page?arg1=val1arg2=val2; so the is rendered as amp; Cheers, Martin That is actually the correct behavior and it shouldn't be causing a problem in your browser. Are you seeing a problem? http://htmlhelp.com/tools/validator/problems.html#amp Josh On Mon, Mar 17, 2008 at 1:18 PM, Martin Grotzke [EMAIL PROTECTED] wrote: Hi, I have a an html element (iframe) that get's a property of my page class (the current query string) appended to its src attribute. The query string may contain the char, which always gets expanded as amp;. Is there any possibility to prevent T5 from encoding this char? Thanx cheers, Martin -- -- TheDailyTube.com. Sign up and get the best new videos on the internet delivered fresh to your inbox. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AW: [T5] How to get ampersand () rendered raw / not encoded as amp;?
Holy dude, I forget. Just use OutputRaw this way: t:outputraw value=query/ instead of: t:output value=query/ First one writes the raw from of the query leaving intact (and all other chars) and the second one would touch it. check out the source for this little component to tweak the filtering / unfiltering as needed (URL-Encoding?). The component in question is org.apache.tapestry.corelib.components.OutputRaw. Cheers, Martin (Kersten) -Ursprüngliche Nachricht- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im Auftrag von Josh Canfield Gesendet: Dienstag, 18. März 2008 18:06 An: Tapestry users Betreff: Re: [T5] How to get ampersand () rendered raw / not encoded as amp;? Hi Martin, I'm confused by your statement: I would say that a request parameter appended with amp;param=value would be seen by the server as amp;param instead of just param. Does this mean that you are seeing a problem on the server side? What you are describing is not what I would expect, if you are seeing this then there might be something else going on. Josh On Tue, Mar 18, 2008 at 7:41 AM, Martin Grotzke [EMAIL PROTECTED] wrote: Hi, On Tue, 2008-03-18 at 14:19 +0100, Chris Lewis wrote: Martin, I'm guessing your mail client converted Josh's message because it rendered the in the url as amp; - just as you have explained and shown. Ok, thanx :) As he said, url's with amp; in place of are actually correct and should not cause problems (I personally have never seen these urls cause any). I would say that a request parameter appended with amp;param=value would be seen by the server as amp;param instead of just param. Cheers, Martin chris Martin Grotzke wrote: On Mon, 2008-03-17 at 15:24 -0700, Josh Canfield wrote: If I am understanding you correctly, you are getting something like this in your source: iframe src=http://host/page?arg1=val1arg2=val2;/iframe Nope, unfortunately I get src=http://host/page?arg1=val1arg2=val2; so the is rendered as amp; Cheers, Martin That is actually the correct behavior and it shouldn't be causing a problem in your browser. Are you seeing a problem? http://htmlhelp.com/tools/validator/problems.html#amp Josh On Mon, Mar 17, 2008 at 1:18 PM, Martin Grotzke [EMAIL PROTECTED] wrote: Hi, I have a an html element (iframe) that get's a property of my page class (the current query string) appended to its src attribute. The query string may contain the char, which always gets expanded as amp;. Is there any possibility to prevent T5 from encoding this char? Thanx cheers, Martin -- -- TheDailyTube.com. Sign up and get the best new videos on the internet delivered fresh to your inbox. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [T5] How to get ampersand () rendered raw / not encoded as amp;?
Hi, On Tue, 2008-03-18 at 17:51 +0100, Filip S. Adamsen wrote: I would say that a request parameter appended with amp;param=value would be seen by the server as amp;param instead of just param. W3C says otherwise: With HTML, the browser translates amp; to so the Web server would only see and not amp; in the query string of the request. http://htmlhelp.com/tools/validator/problems.html#amp It's not a problem. I see the exact same behaviour and it's working just fine. :) You're right! It was indeed only an asumption that it would not work, I wasn't aware that browsers not only translate entities for what is going to the user but also for such things - what is requested elsewhere... New day - a new thing learned, great :) Thanx cheers, Martin On Tue, 2008-03-18 at 17:51 +0100, Filip S. Adamsen wrote: Hi, On 2008-03-18 15:41, Martin Grotzke wrote: Hi, On Tue, 2008-03-18 at 14:19 +0100, Chris Lewis wrote: Martin, I'm guessing your mail client converted Josh's message because it rendered the in the url as amp; - just as you have explained and shown. Ok, thanx :) As he said, url's with amp; in place of are actually correct and should not cause problems (I personally have never seen these urls cause any). I would say that a request parameter appended with amp;param=value would be seen by the server as amp;param instead of just param. W3C says otherwise: With HTML, the browser translates amp; to so the Web server would only see and not amp; in the query string of the request. http://htmlhelp.com/tools/validator/problems.html#amp It's not a problem. I see the exact same behaviour and it's working just fine. :) -Filip Cheers, Martin chris Martin Grotzke wrote: On Mon, 2008-03-17 at 15:24 -0700, Josh Canfield wrote: If I am understanding you correctly, you are getting something like this in your source: iframe src=http://host/page?arg1=val1arg2=val2;/iframe Nope, unfortunately I get src=http://host/page?arg1=val1arg2=val2; so the is rendered as amp; Cheers, Martin That is actually the correct behavior and it shouldn't be causing a problem in your browser. Are you seeing a problem? http://htmlhelp.com/tools/validator/problems.html#amp Josh On Mon, Mar 17, 2008 at 1:18 PM, Martin Grotzke [EMAIL PROTECTED] wrote: Hi, I have a an html element (iframe) that get's a property of my page class (the current query string) appended to its src attribute. The query string may contain the char, which always gets expanded as amp;. Is there any possibility to prevent T5 from encoding this char? Thanx cheers, Martin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] signature.asc Description: This is a digitally signed message part
Re: [T5] How to get ampersand () rendered raw / not encoded as amp;?
Hi, On Tue, 2008-03-18 at 10:06 -0700, Josh Canfield wrote: Hi Martin, I'm confused by your statement: I would say that a request parameter appended with amp;param=value would be seen by the server as amp;param instead of just param. Does this mean that you are seeing a problem on the server side? Nope, as I just wrote I simply asumed that - misleadingly ;) Cheers, Martin What you are describing is not what I would expect, if you are seeing this then there might be something else going on. Josh On Tue, Mar 18, 2008 at 7:41 AM, Martin Grotzke [EMAIL PROTECTED] wrote: Hi, On Tue, 2008-03-18 at 14:19 +0100, Chris Lewis wrote: Martin, I'm guessing your mail client converted Josh's message because it rendered the in the url as amp; - just as you have explained and shown. Ok, thanx :) As he said, url's with amp; in place of are actually correct and should not cause problems (I personally have never seen these urls cause any). I would say that a request parameter appended with amp;param=value would be seen by the server as amp;param instead of just param. Cheers, Martin chris Martin Grotzke wrote: On Mon, 2008-03-17 at 15:24 -0700, Josh Canfield wrote: If I am understanding you correctly, you are getting something like this in your source: iframe src=http://host/page?arg1=val1arg2=val2;/iframe Nope, unfortunately I get src=http://host/page?arg1=val1arg2=val2; so the is rendered as amp; Cheers, Martin That is actually the correct behavior and it shouldn't be causing a problem in your browser. Are you seeing a problem? http://htmlhelp.com/tools/validator/problems.html#amp Josh On Mon, Mar 17, 2008 at 1:18 PM, Martin Grotzke [EMAIL PROTECTED] wrote: Hi, I have a an html element (iframe) that get's a property of my page class (the current query string) appended to its src attribute. The query string may contain the char, which always gets expanded as amp;. Is there any possibility to prevent T5 from encoding this char? Thanx cheers, Martin signature.asc Description: This is a digitally signed message part
Re: AW: [T5] How to get ampersand () rendered raw / not encoded as amp;?
Hi Martin (K.) :)
just to have this complete, the template part was this:
iframe src=http://foo/?foo=bar#38;${queryString};
with queryString beeing a page property...
Cheers,
Martin
On Tue, 2008-03-18 at 18:11 +0100, Martin Kersten wrote:
Hi Martin,
how is the query string is appended? There is always a difference in
writing
text and html. If you write text everything gets converted. If you write html
(raw)
everything will work.
Please just post the tml-part in question. Maybe we can give a shorty for it.
Cheers,
Martin (Kersten)
-Ursprüngliche Nachricht-
Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im Auftrag von Josh Canfield
Gesendet: Dienstag, 18. März 2008 18:06
An: Tapestry users
Betreff: Re: [T5] How to get ampersand () rendered raw / not encoded as
amp;?
Hi Martin,
I'm confused by your statement:
I would say that a request parameter appended with amp;param=value
would be seen by the server as amp;param instead of just param.
Does this mean that you are seeing a problem on the server side? What you are
describing is not what I would expect, if you are seeing this then there
might be something else going on.
Josh
On Tue, Mar 18, 2008 at 7:41 AM, Martin Grotzke [EMAIL PROTECTED] wrote:
Hi,
On Tue, 2008-03-18 at 14:19 +0100, Chris Lewis wrote:
Martin,
I'm guessing your mail client converted Josh's message because it
rendered the in the url as amp; - just as you have explained and
shown.
Ok, thanx :)
As he said, url's with amp; in place of are actually correct and
should not cause problems (I personally have never seen these urls
cause any).
I would say that a request parameter appended with amp;param=value
would be seen by the server as amp;param instead of just param.
Cheers,
Martin
chris
Martin Grotzke wrote:
On Mon, 2008-03-17 at 15:24 -0700, Josh Canfield wrote:
If I am understanding you correctly, you are getting something
like this in your source:
iframe src=http://host/page?arg1=val1arg2=val2;/iframe
Nope, unfortunately I get src=http://host/page?arg1=val1arg2=val2;
so the is rendered as amp;
Cheers,
Martin
That is actually the correct behavior and it shouldn't be causing
a problem in your browser. Are you seeing a problem?
http://htmlhelp.com/tools/validator/problems.html#amp
Josh
On Mon, Mar 17, 2008 at 1:18 PM, Martin Grotzke
[EMAIL PROTECTED] wrote:
Hi,
I have a an html element (iframe) that get's a property of my
page class (the current query string) appended to its src attribute.
The query string may contain the char, which always gets
expanded as amp;. Is there any possibility to prevent T5 from
encoding this char?
Thanx cheers,
Martin
--
--
TheDailyTube.com. Sign up and get the best new videos on the internet
delivered fresh to your inbox.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
signature.asc
Description: This is a digitally signed message part
[T5] How to get ampersand () rendered raw / not encoded as amp;?
Hi, I have a an html element (iframe) that get's a property of my page class (the current query string) appended to its src attribute. The query string may contain the char, which always gets expanded as amp;. Is there any possibility to prevent T5 from encoding this char? Thanx cheers, Martin signature.asc Description: This is a digitally signed message part
Re: [T5] How to get ampersand () rendered raw / not encoded as amp;?
If I am understanding you correctly, you are getting something like this in your source: iframe src=http://host/page?arg1=val1amp;arg2=val2;/iframe That is actually the correct behavior and it shouldn't be causing a problem in your browser. Are you seeing a problem? http://htmlhelp.com/tools/validator/problems.html#amp Josh On Mon, Mar 17, 2008 at 1:18 PM, Martin Grotzke [EMAIL PROTECTED] wrote: Hi, I have a an html element (iframe) that get's a property of my page class (the current query string) appended to its src attribute. The query string may contain the char, which always gets expanded as amp;. Is there any possibility to prevent T5 from encoding this char? Thanx cheers, Martin -- -- TheDailyTube.com. Sign up and get the best new videos on the internet delivered fresh to your inbox. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
