ssl url problem

[AndiC]

my set up is currently

/cgi-bin
/httpdocs <- http
/httpdocs/acatalog <- catalog
/httpsdocs <-https

the checkout works with https as the cgi-bin can be accessed
form both http and https.

However, graphics can not be fould they point to
https://mysite/acatalog of course this does not work
as there are in /httpdocs/acatalog which would be http://mysite/acatalog.

if i try to change the catalog url in ssl network settings to
http://mysite/acatalog it just changes to https://mysite/acatalog

am i going to have to copy these files across?

as fars as i can see only the cgi-bin realy needs to be accessed via https to make it secure.

regards

AndiC

[AndiC]

oh yes

the css files will also be missing as well as included javascripts
as they only state a file name in the source i guess i will have to copy them across?

is there not away to get actinic to place the files where need?

AndiC

[Pneumatus]

Just a thought... You set SSL on in Business Settings, then 'Configure SSL Settings' - All your normal details are in the first tab... go to the SSL tab and fill in the details as if you were using /httpsdocs instead of /httpdocs

Matt

[AndiC]

i did that now the whole site will not work

it does not put anything into httpsdoc

also under standard i have the setting

FTP

Path from CGI-BIN to acatalog as viewed by ftp server (leave blank uless advised)
= ../httpdocs/acatalog/

this is disabled under ssl surely i would need
to put ../httpsdocs/acatalog/


AndiC

[Darren]

Hi there.

I would suggest contacting your hosting company, and ask them if they can set up a symbolic link from the secure acatalog to the insecure acatalog, that should do it.

[Pneumatus]

Ok... Under you 'Standard' Tab you should have

Catalog URL: http://www.yoursite.com/acatalog/
CGI-Bin URL: http://www.yoursite.com/cgi-bin/
CodeBase: ./
Path From CGI-Bin to acatalog: ../httpdocs

Path to CGI-Bin: /cgi-bin/


Leave the 'as viewed by the web server' one blank

then, in your SSL Tab

Catalog URL: https://www.yoursite.com/acatalog/
CGI-Bin URL: https://www.yoursite.com/cgi-bin/
CodeBase: ./
Path From CGI-Bin to acatalog: ../httpsdocs

Path to CGI-Bin: /cgi-bin/

[Netbit]

I'm having this problem too.

The insecure part of the site works fine, no broken images or anything. But when you go to the Checkout (secure, https) the images are all broken.

Checking out the html source shows that the checkout is trying to reference images from the secure section (https) and not the insecure part (http) where the images actually are.

my server structure:

/httpdocs
/httpsdocs
/cgi-bin

my network settings (standard):

catalog url: http://www.XXX.com/acatalog/
cgi-bin url: http://www.XXX.com/cgi-bin/
codebase: ./
path from cgi-bing to acatalog: ../httpdocs/acatalog/
common settings/website url: http://www.XXX.com/acatalog/
ftp details/path from cgi to acatalog: ../httpdocs/acatalog

my network settings (ssl):

as standard but with https instead of http and "ftp details/path from cgi to acatalog" is greyed out.


Business Settings:

ssl
checkout pages and customer login only

[Netbit]

Pneumatus, i tried your suggested settings but Actinic auto changes the "Path From CGI-Bin to acatalog" to what i've given.

[AndiC]

We have exactly the same problem

[Pneumatus]

I can't seem to replicate you having details greyed out... when I switch to the SSL tab, the only details I have greyed out are 'Path from cgi-bin to acatalog directory as viewed by the FTP server'.

[Pneumatus]

Proof attached

(set to ../httpsdocs/acatalog/ there and ../httpdocs/acatalog/ in the standard tab)

[Netbit]

Yup, thats exactly as I have it. -we are talking about the same field thats greyed out. I also have data in the common settings/website url, as described above.

Somehow we need to figure out how to get the pages on the secure (httpsdocs) section of the site to reference its images on the insecure (httpdocs) section of the site

hmm..

[Darren]

Hello there.

I made a posting earlier on, it has been a busy thread so it was easy to miss.

I suggest contacting your host. They may be able to set up a symbolic link from the secure acatalog to the insecure acatalog. This means when you are browsing to https://mysite/acatalog, it is sourcing the files from the httpd/acatalog folder.

Hope this helps.

[Netbit]

I'll get onto the webhost.. however, we should be able to get this working without their help assuming that we've done everything right.

v7 is pretty new isn't it? perhaps its a bug?

[Pneumatus]

The only implication of that is that you will have all of your catalog pages available over https:// - that means that if someone stumbles across your site on https://, you may have some 'insecure' pages that will cause problems for users getting the insecure content warnings.