On 02/26/2018 12:48 PM, Matthew Wronka wrote: > > http://foo/ and https://foo/ are different URLs > and there's no reason they'd have the same content
just to be clear they are the same URL only they are being accessed using a different communications protocol if a particular "content" is accessible via either protocol then one should very much expect get the same content using either - it is not strictly necessary for that to be the case but it would be unconventional and somewhat deceptive for the web-master to do otherwise the converse is like a file on a FTP server that for some reason gives you a different file if you access it via HTTP e.g. ftp://foo.com/foo.exe http://foo.com/foo.exe one should be very disturbed if those did not return the same file
signature.asc
Description: OpenPGP digital signature
-- http://gnuzilla.gnu.org
