Currently we use either SMB or AFP as File Storage Distribution point on Jamf Pro Server and can use Apache HTTP additionally to enable HTTP/HTTPS downloads.
So in this case we need to setup SMB/AFP first and apache http on the server if we want to enable HTTP/HTTPS downloads, but Apache HTTP can't be used as standalone for configuring File Storage Distribution point.
As Apache HTTP will enable only downloads, but to upload or replicate packages to the distribution point via Jamf Admin.app, the SMB/AFP protocol will be used.
So JAMF has a dependency on SMB. This restricts or rather puts a strain on the enterprise if we want to disable SMB.
Jamf should really work on to enable HTTPS-only distribution point going forward, so we don't need to have two protocols managed at same time.