Separate URL for SSL/Checkout

For general questions and discussions specific to the AbleCommerce 7.0 Asp.Net product.
Post Reply
User avatar
nickc
Captain (CAPT)
Captain (CAPT)
Posts: 276
Joined: Thu Nov 29, 2007 3:48 pm

Separate URL for SSL/Checkout

Post by nickc » Thu Apr 23, 2009 11:48 am

I wonder if someone can comment on how Able passes basket and user context into checkout page when separate URL is used? For example, I fill my basket up at store.domain.com, and click "checkout", which takes me to secure.domain.com. Also, I assume that secure.domain.com needs to be added into the Able license for this to work. Is there additional cost for that?

Thanks,
-Nick

User avatar
nickc
Captain (CAPT)
Captain (CAPT)
Posts: 276
Joined: Thu Nov 29, 2007 3:48 pm

Re: Separate URL for SSL/Checkout

Post by nickc » Tue Apr 28, 2009 9:47 am

Any help here? This is a challenge for me; the redirect must be somewhere in the CommerceBuilder API, which I don't have source for, and I can't test without buying the extra domain first.

User avatar
jmestep
AbleCommerce Angel
Posts: 8164
Joined: Sun Feb 29, 2004 8:04 pm
Location: Dayton, OH
Contact:

Re: Separate URL for SSL/Checkout

Post by jmestep » Tue Apr 28, 2009 12:19 pm

I can look in the source code if you tell me exactly what I am searching for-- some terms.
Judy Estep
Web Developer
jestep@web2market.com
http://www.web2market.com
708-653-3100 x209
New search report plugin for business intelligence:
http://www.web2market.com/Search-Report ... -P154.aspx

User avatar
nickc
Captain (CAPT)
Captain (CAPT)
Posts: 276
Joined: Thu Nov 29, 2007 3:48 pm

Re: Separate URL for SSL/Checkout

Post by nickc » Tue Apr 28, 2009 12:36 pm

Maybe the store setting field that holds the secure url: SSLEncryptedUri?
Or possibly one of the two members exposed by StoreSettingCollection class - EncryptedUri or UnencryptedUri? Wherever those get implemented or also possibly where the <securePages> section from ablecommerce.config is parsed.

Thanks for looking. I'm guessing that some token is passed in the querystring to identify the origin user and then User.Migrate is called, so that might be another thing to look for.

-Nick

Post Reply