[FX.php List] [OFF] Rewrite for forcing http to https possible?

[biscuit technologies]

HI Troy,
that makes perfect sense, it seems like it's going to work just fine.

by the way, your orchids are amazing - very impressive stuff.

- David

On Wed, Sep 24, 2008 at 12:59 PM, Troy Meyers <tcmeyers at troymeyers.com> wrote:
> David,
>
> The only reason we had to deal with this is that we want to continue to support the old CDML URLs from FileMaker 4 that people have embedded in their personal or commercial sites.
>
> We don't currently generate URLs any that have the problems that I've been dealing with in this thread.
>
> Here's a real example, something that is provided as a link in someone else's website:
>
> http://lab.troymeyers.com/flasking/FMPro?-db=cultivarphotos&-op=eq&cultivarphotos%20id%20key=38&-format=cultivphotodftr.htm&-lay=cgi111&-find=
>
> Sure, it's very old and very ugly, but we want to allow it to continue to work.
>
> These days, we'd either distribute the URL in email as:
> http://troymeyers.com/direct/?0938
> so that's it's easy to copy or click (or for those who insist, retype)
>
> ...or internal to the site, as this:
> https://lab.troymeyers.com/flasking/photo.php?id=38
>
> Make sense?
>
> -Troy
>
>
>
>> Hey, that's great!
>>
>> I don't know if this matters or if it's actually related to the NE or
>> something else you've got going on, but one potential gotcha might be
>> that other characters that should be encoded are not - so if I try to go
>> to:
>>
>> https://lab.troymeyers.com/flasking/listing.php?genus=Name+with%20spaces
>>
>> I get a result that makes me think the '+' is being ignored as
>> whitespace.
>>
>> I'm a little confused about where these encoded URLs are coming from,
>> are they hardcoded or being generated dynamically, but I was thinking
>> last night that if they are dynamic you would probably be best turning
>> off whatever is doing that encoding because your problem is actually
>> that you are encoding your URLs twice.
>>
>> If you can't turn off that initial encoding then having your NE rule
>> helps, except it opens you up to having this problem come up again later
>> with newly created URLs that are dynamic and do contain unencoded
>> characters. I was going down a very complicated path where you would use
>> variables in your rewrite rule to intercept these already encoded urls
>> and rewrite them just so you can encode them again.
>>
>> Usually I don't like complicated solutions - because I think it usually
>> means I'm on the wrong track - what do you think?
>>
>> - David
>
> _______________________________________________
> FX.php_List mailing list
> FX.php_List at mail.iviking.org
> http://www.iviking.org/mailman/listinfo/fx.php_list
>