Mascot: The trusted reference standard for protein identification by mass spectrometry for 25 years

Blog

Articles tagged: HTTPS

Return to blog archive

Posted by Ville Koskinen (August 31, 2022)

Downloading UniProt proteomes via new API

The UniProt website received a snazzy facelift in June 2022. Both the browser interface and the REST API were updated. The previous version, now termed legacy website, remains available until the 2022_04 release under a new URL (https://legacy.uniprot.org/) – so there is limited time to compare and admire the improvements! The new API is an almost seamless transition for Mascot [...]

Full article and comments form

Posted by Ville Koskinen (December 16, 2021)

Mascot cluster installation security on Linux

Mascot Server has a built-in cluster mode, where the database search can be executed in parallel on a networked cluster of PCs. This requires no special hardware or operating software. The cluster can consist of ‘commodity’ PCs running Windows or Linux. Cluster mode is usually the most practical option for licences of 5 CPU or more, as discussed in Mascot [...]

Full article and comments form

Posted by Ville Koskinen (November 16, 2021)

Retiring the File Transfer Protocol (FTP)

Mascot Server includes Database Manager, which can be configured to download protein sequence databases from many sources using FTP (File Transfer Protocol), HTTP (Hyper Text Transfer Protocol) and HTTPS (HTTP Secure). FTP is the oldest of these protocols by far, making its first appearance in 1971. Until some years ago, FTP was the best and only choice for large file [...]

Full article and comments form

Posted by John Cottrell (March 14, 2018)

Stepping up security

In late 2016, NCBI dropped support for HTTP requests and restricted their web resources to HTTPS. EBI went HTTPS by default in October 2017 and UniProt has announced that it will go HTTPS-only in June 2018. The UniProt change will cause a problem with Database Manager in older versions of Mascot. This article summarises the effects of turning off HTTP, [...]

Full article and comments form