@Tom: Oh sure, hardlinks are rife and a HTTP 301 might be a bit crude. I favour what Chris suggests.
Getting rather too involved in this no doubt ... but I wonder how we are all defining 'deprecated'. My dictionary says 'in the process of being replaced' --- which I take to mean (employing the principle of least surprise) that during the process it will work until the replacement arrives, at which point it will be decommissioned, retired, removed, dereferenced. For me that means not just firewalling off 21/tcp or stopping the service, but clearly stating in the documentation that $thing is dead. Surely I'm procrastinating with such pedantry here. =) :D -----Original Message----- From: Chris Cappuccio [mailto:[email protected]] Sent: 19 December 2018 22:18 To: Tom Beecher <[email protected]> Cc: Niall Donaghy <[email protected]>; Juniper List <[email protected]>; [email protected]; Saku Ytti <[email protected]> Subject: Re: [j-nsp] ftp.juniper.net Tom Beecher [[email protected]] wrote: > Lots of people (for better or for worse) may have hard linked / > referenced > KB15585 in their documentation, so IMO it's a good idea to leave it up > with a bolded note of depreciation, which is what they did. > Just erase the rest of the KB after this text: NOTE: Use of FTP is deprecated, large file uploads for cases should instead use the SSH FTP (SFTP) process described in KB23337 - How to upload large files to a JTAC Case. Problem solved.
_______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
