Skip to content
This repository has been archived by the owner on Jan 25, 2023. It is now read-only.

Commit

Permalink
Merge pull request #211 from ga4gh-beacon/very_minor_change
Browse files Browse the repository at this point in the history
Change MUST with SHOULD as we agreed in the security review meeting.
  • Loading branch information
sdelatorrep authored Sep 28, 2018
2 parents f79005b + 10b4ec2 commit 1401ea8
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion beacon.md
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@ Due to the needs for data discoverability providing as much metadata as possible

## Protocol essentials

Beacon provides REST API on top of the HTTPS protocol, as specified in RFC 7231. HTTPS (HTTP over SSL) MUST be used instead of regular HTTP because the communication between Beacon server and Beacon client has to be encrypted. The Beacon API has two endpoints: `/` (also known as _Info endpoint_) and `/query`. The _Info endpoint_ provides general metadata about the Beacon instance and dataset(s) included. The query interface is provided by the _Query endpoint_.
Beacon provides REST API on top of the HTTPS protocol, as specified in RFC 7231. HTTPS (HTTP over SSL) SHOULD be used instead of regular HTTP because the communication between Beacon server and Beacon client has to be encrypted. The Beacon API has two endpoints: `/` (also known as _Info endpoint_) and `/query`. The _Info endpoint_ provides general metadata about the Beacon instance and dataset(s) included. The query interface is provided by the _Query endpoint_.

The full complement of Beacon API endpoints, requests and responses is published in [OpenAPI format](https://github.com/ga4gh-beacon/specification/blob/master/beacon.yaml).

Expand Down

0 comments on commit 1401ea8

Please sign in to comment.