[ic] secure submission or not based on button

k palazani at gmx.net
Fri Aug 6 18:04:03 EDT 2004


Grant wrote:

> --- k <palazani at gmx.net> wrote:
> 
> 
>>Grant wrote:
>>
>>
>>>--- k <palazani at gmx.net> wrote:
>>>
>>>
>>>
>>>>Grant wrote:
>>>>
>>>>
>>>>
>>>>>I have two submission buttons on my shopping cart
>>>>>page.  One recalculates the cart's contents and
>>>>>returns to the shopping cart page, and one goes
>>
>>to
>>
>>>>the
>>>>
>>>>
>>>>>checkout page.  I want the form to be submitted
>>>>>securely (https nextpage) if the checkout button
>>>>
>>>>is
>>>>
>>>>
>>>>>clicked, but not securely if the recalculate
>>>>
>>>>button is
>>>>
>>>>
>>>>>clicked.  Is this possible?  I'm guessing it
>>
>>isn't
>>
>>>>>since secure or not seems to be defined for the
>>>>
>>>>entire
>>>>
>>>>
>>>>>form in its action.
>>>>
>>>>Make sure that your basket action is not secure:
>>>>[process secure=0]
>>>>
>>>>Updating your basket now submits the form not
>>>>securely.
>>>>
>>>>Use the Directive AlwaysSecure to secure the form
>>>>submission if your 
>>>>checkout button is pushed.
>>>>
>>>>Add in your catalog.cfg:
>>>>AlwaysSecure login ord/checkout ...
>>>>
>>>>k.
>>>
>>>
>>>That is exactly what I have now.  checkout is
>>>specified as AlwaysSecure, and it works through a
>>>link, but not through an mv_click button that
>>
>>defines
>>
>>>checkout as the mv_nextpage.
>>>
>>>- Grant
>>>
>>
>>But it should work for links also. Ic generates
>>links as secure, if the 
>>target page is defined as AlwaysSecure.
>>
>>I use something like that
>>[page ord/checkout]foo</a>
>>
>>and ic delivers
>>https://...
> 
> 
> Yes, the AlwaysSecure links work great, but
> AlwaysSecure doesn't seem to kick in with form
> submission and mv_nextpage.
> 

Yes, you are right. That was the reason why I am using the link, but I 
forgot about it, now its back ;-)

k.




More information about the interchange-users mailing list