(RESOLVED) Will it ever be implemented? HTTPS

[ClockworkCupcake]

CraigyMc said:

pistonheads.co.uk was the original site.

pistonheads.com was added many, many years later

The content is identical. The cert should have the .co.uk domain added to it.

I think petrolheads.co.uk might have been the original site (unless you count the Yahoo Groups. )

[CraigyMc]

ClockworkCupcake said:

CraigyMc said:

pistonheads.co.uk was the original site.

pistonheads.com was added many, many years later

The content is identical. The cert should have the .co.uk domain added to it.

I think petrolheads.co.uk might have been the original site (unless you count the Yahoo Groups. )

I bow to your wisdom.

I'm just a youngun by comparison...

[stuart-b]

Durzel said:

Tell that to Google and the crawled links

PH/Haymarket ought to be permanently redirecting .co.uk to .com if it's the same content lest they get into a bit of grief for duplicate content, etc, or buy another SSL certificate I guess?

If you specify it as a canonical link there's no issue with duplicate content.

[amokwa]

PistonTechs said:

We can now announce a further update on the work to implement HTTPS on PistonHeads.


We do appreciate your patience surrounding this and continue to welcome your feedback.

Thanks,

Laura – for and on behalf of the tech team

Amazing Grace !

[adam quantrill]

i haven't bothered reading this thread but has someone already mentioned the thumbsnap https problem?

I get this:

This site can’t provide a secure connection

thumbsnap.com uses an unsupported protocol.
ERR_SSL_VERSION_OR_CIPHER_MISMATCH

It's using an old version of SSL that don't work with Chrome (or various other browsers).

Previously, thumbsnap just used http, and all was well.

[lewisco]

adam quantrill said:

i haven't bothered reading this thread but has someone already mentioned the thumbsnap https problem?

I get this:

This site can’t provide a secure connection

thumbsnap.com uses an unsupported protocol.
ERR_SSL_VERSION_OR_CIPHER_MISMATCH

It's using an old version of SSL that don't work with Chrome (or various other browsers).

Previously, thumbsnap just used http, and all was well.

Looking at the thumbsnap cert it was issued on the 9th May and is now SHA-256 which is supported. Maybe restart your browser and try again.

[adam quantrill]

It's the SSL version that's the problem...

"The client and server don't support a common SSL protocol version or cipher suite. This is likely to be caused when the server needs RC4, which is no longer considered secure"

If you really want I'll crank up wireshark for you and add a pcap. But I'd rather not because my hobby will then be polluted by my job!

[adam quantrill]

Interestingly thumbsnap links are now coming up as (for example)

http://s194.photobucket.com/user/mk1fan/media/Wend...

thank god they have seen sense.

[adam quantrill]

Now the image upload has been broken by a similar problem:

"The client and server don't support a common SSL protocol version or cipher "

Up till now I have been working around the image display problem by manually re-entering image links with "http" instead of "https", which is tedious. But this latest problem is intractable by manual methods.

[adam quantrill]

Heloooo? Anyone there?

[jj5b]

the breadcrumbs have div class="breadcrumbs"><a href="http://www.pistonheads. Change to https

[ClockworkCupcake]