(RESOLVED) Will it ever be implemented? HTTPS

[0000]

Jack Mansfield said:

I'd love to go into huge detail about some of the problems we encounter, but unfortunately I am not part of the development team and would be extremely wrong if I tried to do so! ... I'm not quite sure what else you would expect from me, as I'm pretty much a middle man in this area.

Be the middle man and ask a dev for a couple of sentences on it?

There is a dev, isn't there?

[Monkeylegend]

0000 said:

Jack Mansfield said:

I'd love to go into huge detail about some of the problems we encounter, but unfortunately I am not part of the development team and would be extremely wrong if I tried to do so! ... I'm not quite sure what else you would expect from me, as I'm pretty much a middle man in this area.

Be the middle man and ask a dev for a couple of sentences on it?

There is a dev, isn't there?

Stop making sensible and obvious suggestions, it will only muddy the waters

[pincher]

On the 22nd February PistonTechs said:

We have some further updates on the implementation of HTTPS on PistonHeads.

As mentioned in a previous update on 2 Feb, this work is being done in stages with the highest priority being the implementation of HTTPS on all pages that have personal data (i.e. login, registration, change password, email confirmation and account details). We have completed the latter work, but it has some critical dependencies that need to be worked out before we can release it. We are aiming to be able to provide timeframes on when this work will be released next week at which point we will provide another update.

Thanks - Laura on behalf of the Tech team

Did I miss the update?

[ClockworkCupcake]

[SystemParanoia]

So... It has come to this!

[eldar]

well it be on to this, even.

[dmsims]

Look, we've been busy

[PistonTechs]

We have an update on the progression of work to implement HTTPS on PistonHeads.

As mentioned before, there are three parts to this work...

1/ Implementing HTTPS on all pages that have personal data (i.e. login, registration, change password, email confirmation and account details)
2/ Implementing HTTPS on the rest of the PistonHeads site
3/ Ensure all ads across the site are served via HTTPS

Part 1/ has been our highest priority and we are happy to say that this has been released today, 21 March 2017.

In regards to part 2/ and 3/, we are making good progress on these stages and are working to be able to give more detail on timeframes soon.

Laura - on behalf of of the tech team

[budgie smuggler]

PistonTechs said:

We have an update on the progression of work to implement HTTPS on PistonHeads.

As mentioned before, there are three parts to this work...

1/ Implementing HTTPS on all pages that have personal data (i.e. login, registration, change password, email confirmation and account details)
2/ Implementing HTTPS on the rest of the PistonHeads site
3/ Ensure all ads across the site are served via HTTPS

Part 1/ has been our highest priority and we are happy to say that this has been released today, 21 March 2017.

In regards to part 2/ and 3/, we are making good progress on these stages and are working to be able to give more detail on timeframes soon.

Laura - on behalf of of the tech team

Thanks

[PoleDriver]

YAY! Chrome doesn't complain when I login now!

[VEA]

I don't know why I feel like congratulations are in order...

[Megaflow]

PistonTechs said:

We have an update on the progression of work to implement HTTPS on PistonHeads.

As mentioned before, there are three parts to this work...

1/ Implementing HTTPS on all pages that have personal data (i.e. login, registration, change password, email confirmation and account details)
2/ Implementing HTTPS on the rest of the PistonHeads site
3/ Ensure all ads across the site are served via HTTPS

Part 1/ has been our highest priority and we are happy to say that this has been released today, 21 March 2017.

In regards to part 2/ and 3/, we are making good progress on these stages and are working to be able to give more detail on timeframes soon.

Laura - on behalf of of the tech team

Welcome to the 21st century...

[pincher]

At last!

[PistonTechs]

Thank you for letting us know about these issues. We are having a hard time trying to replicate the issues being described so could you please provide some more details about the device type and browser you are using where you experience these issues and if you are able to replicate the issues?

Thank you,

Laura - on behalf of the tech team

[Vaud]

anonymous said:

[redacted]

I doubt "torbrowser" is on the list of most companies test suite to be honest... it has <2M users globally IIRC...

[Old Tyke]

I am no expert in such matters, but.. some VPNs and cover-yer-arse browsers like that force https as default unless you turn it off. Could the reason why you're stuck in an infinite loop be because only the login page is https and the rest of the site pages are still http? If you have it set to force https everywhere then you won't be able to access this site apart from the login page.

[0000]

[Funk]

0000 said:

It's just like reading the C&P MS Community 'support' replies...!

99% of the time it's a generic template response asking for content the OP has already supplied as they've not actually READ the post. In most cases, the eventual 'answers' are nothing to do with the problem described and it's other users who end up helping out most...

[Craikeybaby]

Haymarket have issued a press release about a £50m investment in their automotive brands, including Pistonheads. Technology, innovation and an increased headcount were all mentioned too, so hopefully things like https can be sorted.

[Turn7]

Craikeybaby said:

Haymarket have issued a press release about a £50m investment in their automotive brands, including Pistonheads. Technology, innovation and an increased headcount were all mentioned too, so hopefully things like https can be sorted.

....of which about 45p will be spent on the forums.....