Skip to content
RupaliM edited this page Jul 2, 2019 · 3 revisions
URL/API RequestMethod Pages
Globle_Search_API GET Globle Search
Glycan_Search_init_API GET Glycan_Search page
glycan_search_simple_API POST Glycan_Search page
Glycan_Search_API POST Glycan_Search page
Protein_Search_init_API GET Protein_Search page, GlycoProtein_Search page
Protein_search_simple_API POST Protein_Search page, GlycoProtein_Search page
Protein_Search_API POST Protein_Search page, GlycoProtein_Search page
Glycan_list_API POST Glycan_list, QuickGlycan_list_page
Protein_list_API POST Protein_list, QuickProtein_list_page, GlycoProtein_list
Protein_Detail_API POST Protein_Detail_page, GlycoProtein_Detail_page
Glycan_Detail_API POST Glycan_Detail_page
Motif_Detail_API POST Motif_Detail_page
Usecases_API POST Quick_search_page
Typeahead_API POST All_Search_page
Log_API POST ALL Pages
AUTH_API POST ALL Pages
Contact_API POST ALL Pages, Feedback widget
* POST is also more secure than GET, because you aren't sticking information into a URL.
  • Using GET as the method for an HTML form that collects a password or other sensitive information is not the best idea.

  • Use GET when it's safe to allow a person to call an action.

  • POST can transmit a larger amount of information than GET. 'POST' has no size restrictions for transmitted data, whilst 'GET' is limited to 2048 characters.

  • Use POST for destructive actions such as creation, editing, and deletion, because you can't hit a POST action in the address bar of your browser