Spy shows incorrect URL's

I am tracking https based site . Everything gets tracked just fine except the Spy - it shows links as http, which makes them not clickable because the site doesn't re-direct automatically. How come that all other pages track https URLs correctly and Spy doesn't? Any workaround?

@dmiperl: Clicky strips the https uri prefix from all links, but as far as I see outgoing links are handled the same way in the Visitor Action Log and in Spy (i.e. I am surprised that you're seeing a difference in Spy, I checked several of my websites before writing this). Could the reason be a www vs non-www issue? How have you set up your hostname in Settings->Preferences->Preferences (https://clicky.com/stats/prefs-site?site_id=xxxxxx)?

Although I've been non-helpful so far, I still feel compelled to ask why you haven't set up automatic redirection from http to https if your website supports secure connections? Possible duplicate content issues aside, the purpose of https is defeated if users can simply load the http version whenever they feel like it.

Ivan A.

Ivan,
Thank you for the answer.
My site is not www, in the preferences I've only used the host name.
Visitor Action Log and other Content/Pages all have perfect clickable links (https).

But in the Spy the links are http and send you to the cosmos.
Because links are targeted to SSL server port, it refuses to redirect, not sure it's even possible.
For example, the spy shows link: http://myhost:8443/path...
The 8443 port on server side is SSL, so server barfs the error to this.
I think Spy is simply showing wrong URL, perhaps my case triggers some subtle bug there.
Or I am missing some setup trick?

@dmiperl: Heh, weird indeed... I think you should shoot an email to [email protected], this does look like a borderline bug and something they should look into. I haven't run SSL on a custom port to know if it works, but it does look like something that could confuse Clicky.

Ivan A.

Ok I fixed this.

You really ought to configure your server to allow HTTP and then redirect to HTTPS though.

Thank you very much for the fix, it works!