Peter J. Farrell wrote:
So URLs like this break:http://www.example.com/index.cm/go/home/?referrer=google This doesn't seem be expected behavior and the RFC spec says the query string should be there even with the path info defined so I'm thinking this is a problem with the filter. Thoughts?
Interesting--my initial reaction is that I'm not sure how you'd mix and match /name/value with ?name=value. In other words as I look at it, it makes sense that it'd break because if you translate this out, it becomes:
http://example.com/index.cfm?go=home?referer=googleSo the question is should the SES filter figure that all out or is that just a URL syntax that doesn't make sense?
To put it another way, if you're using SES URLs, why are you not using this as the URL?
http://example.com/index.cfm/go/home/referer/googleI know that's not an answer but I thought it might kickstart any underlying technical discussions that need to happen.
-- Matt Woodward [email protected] http://www.mattwoodward.com/blogPlease do not send me proprietary file formats such as Word, PowerPoint, etc. as attachments.
http://www.gnu.org/philosophy/no-word-attachments.html
smime.p7s
Description: S/MIME Cryptographic Signature
