IWETHEY v. 0.3.0 | TODO
1,095 registered users | 0 active users | 0 LpH | Statistics
Login | Create New User
IWETHEY Banner

Welcome to IWETHEY!

New HTTP parameters and escaping.
I've got a bit of a wierd problem on my work HTTP server with an external service and I'm not sure who is actually in the right.

The core of the problem is whether an HTML-escaped ampersand is legal in a HTTP redirect.

We have an ampersand in a link functioning as a parameter separator, as languages like PHP have been doing for years. We're using an external service to provide unsubsubscribe links and they're using a tracking link which redirects to our unsubscribe link. Unfortuantely, they're HTML-escaping the URL, even in the HTTP redirect, resulting in a non-working link. They shouldn't be doing that, right?

Wade.

Q:Is it proper to eat cheeseburgers with your fingers?
A:No, the fingers should be eaten separately.
New Parameter Escaping is a nono.
We have use about 5 parameters in some mailing lists.

This means they need to be real and not escaped.
New That's what I thought.
I found an RFC that ... uh, didn't dispute that. (It doesn't actually say "do not HTML escape" -- but reading it in context and it's clear that HTML escaping is not wanted there.)

Wade.

Q:Is it proper to eat cheeseburgers with your fingers?
A:No, the fingers should be eaten separately.
     HTTP parameters and escaping. - (static) - (2)
         Parameter Escaping is a nono. - (folkert) - (1)
             That's what I thought. - (static)

I have this theory about the Brontosaurus...
50 ms