close ad
Databridge V2 with MySQLi support IS Now Available!
open ad
View Menu

Technical Support Forums

Free, outstanding support from WebAssist and your colleagues

rating

eCart Security

Thread began 7/07/2011 9:59 am by stephenjohnston249928 | Last modified 7/07/2011 10:38 am by Jason Byrnes | 754 views | 3 replies |

stephenjohnston249928

eCart Security

I've used eCart before, but this is the first time I have used it with paypal pro. It seems to be connecting fine to the sandbox. However I have some security concerns.

1. I notice that some pages contain all the API user, password, signature in them - and these are in the public part of the site (eg checkout.php). Is this safe? Surely if someone downloads that page or uses a tool like 'Site Import', they'll have the api access details?

2. As my other eCart sites were just paypal std, I had no need for SSL. But I'll need to add SSL for the pro integration, which is fine. But as an SSL novice (my host will install for me) - do I need to place all the https required pages in a separate folder from the non ssl files. And do I need to put all ssl assets (images, css, javascript, webassist files etc etc) in the same folder as the SSL files. Or will I get a 'This page contains both secure and non secure......' warning if I don't.

Sign in to reply to this post

Jason ByrnesWebAssist

1) Those details are in the php source code, the only way someone could download that information is by gaining FTP access to the server.

site import will only download the browser source, not the raw php code.

2) This depends on how your host configures the server. Some hosts set it up so that the SSL pages have their own directory, others dont.

the 'This page contains both secure and non secure......' error happens if you Fully Qualified links to assets that use http protocol, for example:
<img src="http://mydomain/images/image.jpg" />

if the link is relative link:
<img src="images/image.jpg" />

you wont get that error.

Sign in to reply to this post

stephenjohnston249928

Thanks Jason,

Once the site is live all ftp & sftp/ssh will be disabled as they'll no longer be needed - so as long as the php code is safe (I did look at the live pages source code and it was fine, as you say).

The host will provide a full SSL using domain.com, not as a subdomain or specific folder.

And all the links are relative links.

So the only precaution would be to use .htaccess to prevent the secure pages from being viewed as non ssl. Or is that not necessary?

Many thanks for your response(s).

Sign in to reply to this post

Jason ByrnesWebAssist

yes, you should make sure the checkout pages cannot be accessed by the non ssl address.

Sign in to reply to this post

Build websites with a little help from your friends

Your friends over here at WebAssist! These Dreamweaver extensions will assist you in building unlimited, custom websites.

Build websites from already-built web applications

These out-of-the-box solutions provide you proven, tested applications that can be up and running now.  Build a store, a gallery, or a web-based email solution.

Want your website pre-built and hosted?

Close Windowclose

Rate your experience or provide feedback on this page

Account or customer service questions?
Please user our contact form.

Need technical support?
Please visit support to ask a question

Content

rating

Layout

rating

Ease of use

rating

security code refresh image

We do not respond to comments submitted from this page directly, but we do read and analyze any feedback and will use it to help make your experience better in the future.

Close Windowclose

We were unable to retrieve the attached file

Close Windowclose

Attach and remove files

add attachmentAdd attachment
Close Windowclose

Enter the URL you would like to link to in your post

Close Windowclose

This is how you use right click RTF editing

Enable right click RTF editing option allows you to add html markup into your tutorial such as images, bulleted lists, files and more...

-- click to close --

Uploading file...