Replace HTTP links with HTTPS

[umangvaghela123]

change HTTP Link To HTTPS.
example

old URL :
​http://codex.wordpress.org/WordPress.org_API

Secure URl.
​https://codex.wordpress.org/WordPress.org_API

[umangvaghela123]

update link

[mitraval192]

Add secure link on WordPress TV site

[adnan.limdi]

Add secure link on WordPress org site

[adnan.limdi]

Add secure link on Wordcamp org site

[ronakganatra]

add secure link in documentation of profiles.wordpress.org

[rushabh4486]

Link is not secure.

[grapplerulrich]

Thank you all for the patches. Most of the URLs automatically redirect to the HTTPS version so this does not have a high prio.

@umangvaghela123 What areas have you worked on updating the patch?
@mitraval192 Are these the only links in WordPress.tv that are not HTTPS?
@adnan.limdi Are these the only links in the API that are not HTTPS? Do all of these links still work? You have added trailing spaces in one of the lines.
@ronakganatra Are all of the other links in profiles.wordpress.org otherwise with HTTPS?
@rushabh4486 As modernizr is a third-party script we should not be making changes to it directly. You have changed the URL in the POT file but not in original source. Are all other links with HTTPS in browsehappy.com?

[ronakganatra]

Replying to grapplerulrich:

Thank you all for the patches. Most of the URLs automatically redirect to the HTTPS version so this does not have a high prio.
@ronakganatra Are all of the other links in profiles.wordpress.org otherwise with HTTPS?

Hello @grapplerulrich ,

Thanks for reviewing the patch and respond to this ticket. I can understand that this automatically redirect to https but I have attached a patch for improvements.

[adnan.limdi]

Remove Space

[SergeyBiryukov]

#3129 was marked as a duplicate.

[umangvaghela123]

Hello @grapplerulrich

I have just replaced http WordPress codex link to HTTPS.

We know that some of the link redirect to the http, but it is fine if we change the link those have secure link.There are many place where link is http but we do not change because it is not secure.

Thank you @grapplerulrich and all

[grapplerulrich]

I can understand that this automatically redirect to https but I have attached a patch for improvements.

I understand that you uploaded a patch and I looked at it. My question was was if all HTTP URLs were changed to HTTPS.

There is no point in everyone just changing the HTTP links in one file. If we are going to make the change then it should be correctly.

[coffee2code]

In 5936:

Browse Happy API: Update URLs for browser homepages to be HTTPS.

Also changes the URL for IE (which has long since redirected) to a more upgrade-specific page.

Props adnanlimdi.
See #3120.

[rushabh4486]

Replying to grapplerulrich:

Thank you all for the patches. Most of the URLs automatically redirect to the HTTPS version so this does not have a high prio.

@umangvaghela123 What areas have you worked on updating the patch?
@mitraval192 Are these the only links in WordPress.tv that are not HTTPS?
@adnan.limdi Are these the only links in the API that are not HTTPS? Do all of these links still work? You have added trailing spaces in one of the lines.
@ronakganatra Are all of the other links in profiles.wordpress.org otherwise with HTTPS?
@rushabh4486 As modernizr is a third-party script we should not be making changes to it directly. You have changed the URL in the POT file but not in original source. Are all other links with HTTPS in browsehappy.com?

@grapplerulrich I have changed all links in browsehappy.com directory. There are no any link for change.

[ronakganatra]

Replying to grapplerulrich:

I can understand that this automatically redirect to https but I have attached a patch for improvements.

I understand that you uploaded a patch and I looked at it. My question was was if all HTTP URLs were changed to HTTPS.

There is no point in everyone just changing the HTTP links in one file. If we are going to make the change then it should be correctly.

Yes, in profiles.wordpress.org I have changed links to secure.

[dd32]

Looks like a few of the patches here still haven't been committed.
However, it's all in old code and redirects safely, so this isn't exactly a high priority.

[pratikthink]

#3652 was marked as a duplicate.

[coffee2code]

In 8230:

WordPress.tv: Update URLs to HTTPS where possible.

Props mitraval192, coffee2code.
See #3120.

[coffee2code]

In 8231:

Jobs: Update URLs to HTTPS where possible.

See #3120.

[coffee2code]

In 8232:

Jobs Theme: Update URLs to HTTPS where possible or to new URLs for those that now redirect.

Props umangvaghela123, coffee2code.
See #3120.

[coffee2code]

In 8233:

Developer: Update URLs in inline documentation to HTTPS where possible or to new URLs for those that now redirect.

Props umangvaghela123, coffee2code.
See #3120.

[coffee2code]

In 8234:

Breathe: Update Codex URL in inline documentation to updated URL in DevHub.

Props umangvaghela123, coffee2code.
See #3120.

[coffee2code]

In 8240:

apps.wordpress.org: Update URLs to HTTPS where possible or to new URLs for those that now redirect.

Props umangvaghela123, coffee2code.
See #3120.

[dd32]

In 8369:

WordPress.TV: Use SSL links in blog.wordpress.tv.

See #3120.

[coffee2code]

In 8440:

Plugin Directory: Update URLs to HTTPS where possible.

Props umangvaghela123, coffee2code.
See #3120.

[dd32]

I'm going to close this ticket as fixed.

If there's any more cases spotted, please open a new ticket.