New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Check whats causing the broken security lock for https://doesliverpool.com #602

Closed
ghost opened this Issue Nov 10, 2017 · 6 comments

Comments

Projects
None yet
2 participants
@ghost

ghost commented Nov 10, 2017

Just to let you know. The green lock doesn't appear for the main Does web address of https://doesliverpool.com. It seems to be that mixed content are used because the certificate is within date until 2018. So it's usually external media or static files not being served over http://. The https://doesliverpool assumes a wildcard certificate, suggesting it's not a sub-domain mismatch.

I'm not involved with the website in anyway and I'm only starting to get involed with DoES. So maybe something to cover in the next website meeting.

@ghost

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost Nov 10, 2017

Had a scan over the source code. Seems to be some Twitter links are using http://, other Twitter links are using https://. One or two other using http:// too. Changing them to https:// should sort it.

ghost commented Nov 10, 2017

Had a scan over the source code. Seems to be some Twitter links are using http://, other Twitter links are using https://. One or two other using http:// too. Changing them to https:// should sort it.

@johnmckerrell

This comment has been minimized.

Show comment
Hide comment
@johnmckerrell

johnmckerrell Nov 11, 2017

Member
Member

johnmckerrell commented Nov 11, 2017

@ghost

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost Nov 12, 2017

It's working now on my side... which is funny because some of the those Twitter links I thought was causing it are still there.

Maybe you need to wait for the server to refresh it's own cache. I think new visitors would get the green padlock now.

ghost commented Nov 12, 2017

It's working now on my side... which is funny because some of the those Twitter links I thought was causing it are still there.

Maybe you need to wait for the server to refresh it's own cache. I think new visitors would get the green padlock now.

@johnmckerrell

This comment has been minimized.

Show comment
Hide comment
@johnmckerrell

johnmckerrell Nov 12, 2017

Member
Member

johnmckerrell commented Nov 12, 2017

@ghost

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost Nov 14, 2017

Ok. I'll leave it open until you give the nod.

ghost commented Nov 14, 2017

Ok. I'll leave it open until you give the nod.

@amcewen

This comment has been minimized.

Show comment
Hide comment
@amcewen

amcewen Dec 4, 2017

Member

I've found the problem that was causing the Twitter images to not be https, and fixed DoESLiverpool/weeknote-generator#23, so it should now all be sorted. At present it doesn't have the padlock, but that's because the older weeknotes on the front page don't have https images in them.

Member

amcewen commented Dec 4, 2017

I've found the problem that was causing the Twitter images to not be https, and fixed DoESLiverpool/weeknote-generator#23, so it should now all be sorted. At present it doesn't have the padlock, but that's because the older weeknotes on the front page don't have https images in them.

@amcewen amcewen closed this Dec 4, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment