Skip to main content
Commonmark migration
Source Link

The sidebar on https://codereview.stackexchange.com/questions/ask links to http://meta.stackexchange.com/q/129598. Visiting this results in a redirect to the HTTPS version of that site. If HTTPS Everywhere is installed it also results in having to disable HTTPS Everywhere on that domain to load the redirect. It should instead link to https://meta.stackexchange.com/q/129598 to avoid both these issues.

It also links to http://meta.codereview.stackexchange.com/q/2436. This is even worse, because after the HTTPS Everywhere prompt it redirects to https://meta.codereview.stackexchange.com/q/2436, which has an invalid TLS configuration.

Here's the relevant extracts of the page (my line-breaks):

If your code is incomplete or not working, you should ask for help
<a href="http://meta.stackexchange.com/q/129598">on another site</a>.
  
>We recommend reading our
<a href="http://meta.codereview.stackexchange.com/q/2436">Guide to
Asking Questions</a>.

Here's what I see in my browser:

Security risk warning

This link should instead be https://codereview.meta.stackexchange.com/q/2436.

PS/brag: I found these using the Insecure Links Highlighter Firefox plugin.

The sidebar on https://codereview.stackexchange.com/questions/ask links to http://meta.stackexchange.com/q/129598. Visiting this results in a redirect to the HTTPS version of that site. If HTTPS Everywhere is installed it also results in having to disable HTTPS Everywhere on that domain to load the redirect. It should instead link to https://meta.stackexchange.com/q/129598 to avoid both these issues.

It also links to http://meta.codereview.stackexchange.com/q/2436. This is even worse, because after the HTTPS Everywhere prompt it redirects to https://meta.codereview.stackexchange.com/q/2436, which has an invalid TLS configuration.

Here's the relevant extracts of the page (my line-breaks):

If your code is incomplete or not working, you should ask for help
<a href="http://meta.stackexchange.com/q/129598">on another site</a>.
 >We recommend reading our
<a href="http://meta.codereview.stackexchange.com/q/2436">Guide to
Asking Questions</a>.

Here's what I see in my browser:

Security risk warning

This link should instead be https://codereview.meta.stackexchange.com/q/2436.

PS/brag: I found these using the Insecure Links Highlighter Firefox plugin.

The sidebar on https://codereview.stackexchange.com/questions/ask links to http://meta.stackexchange.com/q/129598. Visiting this results in a redirect to the HTTPS version of that site. If HTTPS Everywhere is installed it also results in having to disable HTTPS Everywhere on that domain to load the redirect. It should instead link to https://meta.stackexchange.com/q/129598 to avoid both these issues.

It also links to http://meta.codereview.stackexchange.com/q/2436. This is even worse, because after the HTTPS Everywhere prompt it redirects to https://meta.codereview.stackexchange.com/q/2436, which has an invalid TLS configuration.

Here's the relevant extracts of the page (my line-breaks):

If your code is incomplete or not working, you should ask for help
<a href="http://meta.stackexchange.com/q/129598">on another site</a>.
 
>We recommend reading our
<a href="http://meta.codereview.stackexchange.com/q/2436">Guide to
Asking Questions</a>.

Here's what I see in my browser:

Security risk warning

This link should instead be https://codereview.meta.stackexchange.com/q/2436.

PS/brag: I found these using the Insecure Links Highlighter Firefox plugin.

added 163 characters in body
Source Link
l0b0
  • 9.1k
  • 14
  • 6

The sidebar on https://codereview.stackexchange.com/questions/ask links to http://meta.stackexchange.com/q/129598. Visiting this results in a redirect to the HTTPS version of that site. If HTTPS Everywhere is installed it also results in having to disable HTTPS Everywhere on that domain to load the redirect. It should instead link to https://meta.stackexchange.com/q/129598 to avoid both these issues.

It also links to http://meta.codereview.stackexchange.com/q/2436. This is even worse, because after the HTTPS Everywhere prompt it redirects to https://meta.codereview.stackexchange.com/q/2436, which has an invalid TLS configuration.

Here's the relevant extracts of the page (my line-breaks):

If your code is incomplete or not working, you should ask for help
<a href="http://meta.stackexchange.com/q/129598">on another site</a>.
>We recommend reading our
<a href="http://meta.codereview.stackexchange.com/q/2436">Guide to
Asking Questions</a>.

Here's what I see in my browser:

Security risk warning

This link should instead be https://codereview.meta.stackexchange.com/q/2436.

PS/brag: I found these using the Insecure Links Highlighter Firefox plugin.

The sidebar on https://codereview.stackexchange.com/questions/ask links to http://meta.stackexchange.com/q/129598. Visiting this results in a redirect to the HTTPS version of that site. If HTTPS Everywhere is installed it also results in having to disable HTTPS Everywhere on that domain to load the redirect. It should instead link to https://meta.stackexchange.com/q/129598 to avoid both these issues.

It also links to http://meta.codereview.stackexchange.com/q/2436. This is even worse, because after the HTTPS Everywhere prompt it redirects to https://meta.codereview.stackexchange.com/q/2436, which has an invalid TLS configuration.

Here's the relevant extracts of the page (my line-breaks):

If your code is incomplete or not working, you should ask for help
<a href="http://meta.stackexchange.com/q/129598">on another site</a>.
>We recommend reading our
<a href="http://meta.codereview.stackexchange.com/q/2436">Guide to
Asking Questions</a>.

Here's what I see in my browser:

Security risk warning

This link should instead be https://codereview.meta.stackexchange.com/q/2436.

The sidebar on https://codereview.stackexchange.com/questions/ask links to http://meta.stackexchange.com/q/129598. Visiting this results in a redirect to the HTTPS version of that site. If HTTPS Everywhere is installed it also results in having to disable HTTPS Everywhere on that domain to load the redirect. It should instead link to https://meta.stackexchange.com/q/129598 to avoid both these issues.

It also links to http://meta.codereview.stackexchange.com/q/2436. This is even worse, because after the HTTPS Everywhere prompt it redirects to https://meta.codereview.stackexchange.com/q/2436, which has an invalid TLS configuration.

Here's the relevant extracts of the page (my line-breaks):

If your code is incomplete or not working, you should ask for help
<a href="http://meta.stackexchange.com/q/129598">on another site</a>.
>We recommend reading our
<a href="http://meta.codereview.stackexchange.com/q/2436">Guide to
Asking Questions</a>.

Here's what I see in my browser:

Security risk warning

This link should instead be https://codereview.meta.stackexchange.com/q/2436.

PS/brag: I found these using the Insecure Links Highlighter Firefox plugin.

edited tags
Link
edited tags
Link
Vogel612 Mod
  • 25.5k
  • 1
  • 38
  • 64
Loading
Show the relevant A elements
Source Link
Toby Speight
  • 88.7k
  • 16
  • 34
Loading
added 421 characters in body
Source Link
l0b0
  • 9.1k
  • 14
  • 6
Loading
added 28 characters in body
Source Link
Jamal Mod
  • 35.2k
  • 2
  • 54
  • 106
Loading
Source Link
l0b0
  • 9.1k
  • 14
  • 6
Loading