search

hassanakbar4 / tractive-test

0 stars 0 forks source link

change to 'https' URLs in boilerplate text #333

Closed hassanakbar4 closed 2 years ago

hassanakbar4 commented 7 years ago

component_Version 2 cli resolution_fixed type_task | by arusso@amsl.com

Please change 'http' to 'https' in boilerplate output as follows (for consistency with shift to 'https' URLs in references to RFCs):

1) in Status of This Memo OLD: Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfcNNNN NEW: Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at https://www.rfc-editor.org/info/rfcNNNN

2) in Copyright Notice OLD: (http://trustee.ietf.org/license-info) NEW: (https://trustee.ietf.org/license-info)

Issue migrated from trac:333 at 2021-10-20 18:24:45 +0500

hassanakbar4 commented 7 years ago

@{"email"=>"julian.reschke@gmx.de", "name"=>nil, "username"=>nil} commented

Can we have a cutover date for this, so that old documents will be generated with the correct text as well?

hassanakbar4 commented 7 years ago

@{"email"=>"henrik@levkowetz.com", "name"=>nil, "username"=>nil} changed status from new to closed

hassanakbar4 commented 7 years ago

@{"email"=>"henrik@levkowetz.com", "name"=>nil, "username"=>nil} changed resolution from ` tofixed`

hassanakbar4 commented 7 years ago

@{"email"=>"henrik@levkowetz.com", "name"=>nil, "username"=>nil} commented

Fixed in [2375]:

Changed the use of http: to https: in many places. In the generation of RFCs, the code uses a switchover date of August 21, 2017 when deciding whether to insert http: or https: URLs. In practice, this means that RFCs with a date of September 2017 or later will get https:. Also fixed URL line-breaking prevention to apply to https: URLS. Fixes issue #333.