WordPress.org

Making WordPress.org

Opened 21 months ago

Last modified 2 months ago

#3120 new enhancement

Replace HTTP links with HTTPS

Reported by: umangvaghela123 Owned by:
Milestone: Priority: normal
Component: SSL Keywords: has-patch needs-refresh
Cc:

Description

Attachments (7)

3120.patch (24.3 KB) - added by umangvaghela123 21 months ago.
update link
3120-wordpress-tv.patch (10.5 KB) - added by mitraval192 21 months ago.
Add secure link on WordPress TV site
3120-api-wordpress-org.patch (1.5 KB) - added by adnan.limdi 21 months ago.
Add secure link on WordPress org site
3120-api-wordpress-org.2.patch (1.5 KB) - added by adnan.limdi 21 months ago.
Add secure link on Wordcamp org site
3120 profiles.wordpress.org .diff (1.9 KB) - added by ronakganatra 21 months ago.
add secure link in documentation of profiles.wordpress.org
3120_browsehappy.com.diff (4.8 KB) - added by rushabh4486 21 months ago.
Link is not secure.
3120-api-wordpress-org-3.patch (2.0 KB) - added by adnan.limdi 20 months ago.
Remove Space

Download all attachments as: .zip

Change History (31)

@umangvaghela123
21 months ago

update link

#1 @umangvaghela123
21 months ago

  • Keywords has-patch added
  • Priority changed from normal to high

#2 @umangvaghela123
21 months ago

  • Priority changed from high to normal

@mitraval192
21 months ago

Add secure link on WordPress TV site

@adnan.limdi
21 months ago

Add secure link on WordPress org site

@adnan.limdi
21 months ago

Add secure link on Wordcamp org site

@ronakganatra
21 months ago

add secure link in documentation of profiles.wordpress.org

This ticket was mentioned in Slack in #meta by ronak.ganatra. View the logs.


21 months ago

@rushabh4486
21 months ago

Link is not secure.

This ticket was mentioned in Slack in #meta by rushabhshah. View the logs.


21 months ago

#5 follow-ups: @grapplerulrich
20 months ago

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?

#6 in reply to: ↑ 5 @ronakganatra
20 months ago

  • Type changed from defect to enhancement

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
20 months ago

Remove Space

#7 @SergeyBiryukov
20 months ago

  • Summary changed from Link is not secure( or not proper) to Replace HTTP links with HTTPS

#8 @SergeyBiryukov
20 months ago

#3129 was marked as a duplicate.

#9 @umangvaghela123
20 months ago

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

#10 follow-up: @grapplerulrich
20 months ago

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.

#11 @coffee2code
20 months ago

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.

#12 in reply to: ↑ 5 @rushabh4486
20 months ago

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.

#13 in reply to: ↑ 10 @ronakganatra
20 months ago

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.

#14 @rushabh4486
20 months ago

  • Keywords needs-refresh added

#15 @dd32
17 months ago

  • Component changed from General to SSL

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.

#16 @pratikthink
12 months ago

#3652 was marked as a duplicate.

#17 @coffee2code
3 months ago

In 8230:

WordPress.tv: Update URLs to HTTPS where possible.

Props mitraval192, coffee2code.
See #3120.

#18 @coffee2code
3 months ago

In 8231:

Jobs: Update URLs to HTTPS where possible.

See #3120.

#19 @coffee2code
3 months ago

In 8232:

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

Props umangvaghela123, coffee2code.
See #3120.

#20 @coffee2code
3 months ago

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.

#21 @coffee2code
3 months ago

In 8234:

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

Props umangvaghela123, coffee2code.
See #3120.

#22 @coffee2code
3 months ago

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.

#23 @dd32
3 months ago

In 8369:

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

See #3120.

#24 @coffee2code
2 months ago

In 8440:

Plugin Directory: Update URLs to HTTPS where possible.

Props umangvaghela123, coffee2code.
See #3120.

Note: See TracTickets for help on using tickets.