While the audience is gathering. During breaks etc

Slides:



Advertisements
Similar presentations
Hypertext Transfer PROTOCOL ----HTTP Sen Wang CSE5232 Network Programming.
Advertisements

 The IP address and port combination at which the NetScaler appliance receives client requests for the associated web application.  A public endpoint.
HTTP Hypertext Transfer Protocol. HTTP messages HTTP is the language that web clients and web servers use to talk to each other –HTTP is largely “under.
From Extensibility to Evolvability Once upon a time, HTTP was simple – what happened?
Joey F. George, Dinesh Batra, Joseph S. Valacich, Jeffrey A. Hoffer
HTTP Overview Vijayan Sugumaran School of Business Administration Oakland University.
2/9/2004 Web and HTTP February 9, /9/2004 Assignments Due – Reading and Warmup Work on Message of the Day.
Hypertext Transport Protocol CS Dick Steflik.
 What is it ? What is it ?  URI,URN,URL URI,URN,URL  HTTP – methods HTTP – methods  HTTP Request Packets HTTP Request Packets  HTTP Request Headers.
Rensselaer Polytechnic Institute CSC-432 – Operating Systems David Goldschmidt, Ph.D.
COMMANDLINE OPTIONS IN SSIS -ABHIJIT -SANJAY -SUSHANT.
IT 210 The Internet & World Wide Web introduction.
Overview of Previous Lesson(s) Over View  ASP.NET Pages  Modular in nature and divided into the core sections  Page directives  Code Section  Page.
FTP (File Transfer Protocol) & Telnet
CollectionSpace Service REST-based APIs June 2009 Face-to-face Aron Roberts U.C. Berkeley IST/Data Services.
Chapter 7 Appendix A Object-Oriented Analysis and Design: Use Cases Modern Systems Analysis and Design Seventh Edition Jeffrey A. Hoffer Joey F. George.
CIS679: Lecture 13 r Review of Last Lecture r More on HTTP.
API Crash Course CWU Startup Club. OUTLINE What is an API? Why are API’s useful? What is HTTP? JSON? XML? What is a RESTful API? How do we consume an.
SCIM conference call 4 September Issue #2 Add pagination capability to plural Resource attributes User Group retrieval could be resource intensive,
The Basics of HTTP Jason Dean
RESTful Web Services What is RESTful?
4-1 © Prentice Hall, 2007 Topic 4: Structuring Systems Requirements: Use Case Description and Diagrams Object-Oriented Systems Analysis and Design Joey.
Summary of Changes 00  01 Structured capabilities into 4 separate Capabilites that can be individually negotiated (instead of 3 incremental capabilities):
Web Protocols: HTTP COMP6017 Topics on Web Services Dr Nicholas Gibbins –
CAS Proxying and Web Services The somewhat “easy way” Presented By: Joseph Mitola Programmer/Analyst Office Of The Registrar.
Hypertext Transfer Protocol (HTTP) COMP6218 Web Architecture Dr Nicholas Gibbins –
Windows 10 Common VPN Error Tech Support Number
David Hatten Developer, UrbanCode 17 October 2013
Chapter 7 Appendix A Object-Oriented Analysis and Design: Use Cases
Content from Python Docs.
The Hypertext Transfer Protocol
Better RESTFul API – Best Practices
Web Development Web Servers.
Hypertext Transfer Protocol
Hypertext Transport Protocol
What is REST API ? A REST (Representational State Transfer) Server simply provides access to resources and the REST client accesses and presents the.
JavaScript: ExpressJS Overview
WStore Programmer Guide
HTTP Protocol.
WEB API.
While the audience is gathering. During breaks etc
While the audience is gathering. During breaks etc
SIS DEVOPS COMMUNICATION MODEL SIMULATOR
While the audience is gathering. During breaks etc
CIS16 Application Development Programming with Visual Basic
Forms, cont’d.
While the audience is gathering. During breaks etc
While the audience is gathering. During breaks etc
API DOCUMENTATION Swetha Mohandas Microsoft Connect 2016
Hypertext Transfer Protocol (HTTP)
Web Server Design Week 10 Old Dominion University
While the audience is gathering. During breaks etc
Requests and Server Response Codes
While the audience is gathering. During breaks etc
While the audience is gathering. During breaks etc
While the audience is gathering. During breaks etc
While the audience is gathering. During breaks etc
While the audience is gathering. During breaks etc
While the audience is gathering. During breaks etc
While the audience is gathering. During breaks etc
While the audience is gathering. During breaks etc
While the audience is gathering. During breaks etc
While the audience is gathering. During breaks etc
While the audience is gathering. During breaks etc
How-TO Use STM module tool
While the audience is gathering. During breaks etc
While the audience is gathering. During breaks etc
While the audience is gathering. During breaks etc
While the audience is gathering. During breaks etc
While the audience is gathering. During breaks etc
Presentation transcript:

While the audience is gathering. During breaks etc While the audience is gathering. During breaks etc. Simple messages can be added in bold and white letters on the dark blue sea, eg. ”Welcome!”, ”Back at 15.15”

Common HTTP Response Codes from VIS 200=Successful 202=Accepted 400=Bad Request 401=Unauthorized 403=Forbidden 404=Not Found 405=Method not allowed 500=Internal Server Error 501=Not implemented

References https://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.1 https://httpstatuses.com/

HTTP Code 200 The request has succeeded. [w3.org] The responded message from VIS is either object defined in the swagger (all GET methods) optional relevant ID, such as UVID or local ID

HTTP Code 202 The request has been accepted for processing, but the processing has not been completed. [w3.org] The responded message from VIS is either object defined in the swagger (all GET methods) optional relevant ID, such as UVID or local ID Can be used e.g. by ROS to indicate that the voyage plan has been accepted and route optimization processing will occur

HTTP Code 400 The request could not be understood by the server due to malformed syntax [w3.org] The responded message from VIS is optional descriptive error message that can include relevant ID

HTTP Code 401 The request requires user authentication. [w3.org] The responded message from VIS is optional descriptive error message that can include relevant ID

HTTP Code 403 The server understood the request, but is refusing to fulfill it. [w3.org] The responded message from VIS is optional descriptive error message that can include relevant ID Sent from VIS when actor is not authorized to information.

HTTP Code 404 The server has not found anything matching. [w3.org] The responded message from VIS is optional descriptive error message that can include relevant ID Sent from VIS e.g. when requested voyage plan cannot be found.

HTTP Code 405 The method specified in the Request-Line is not allowed for the resource identified by the Request-URI. [w3.org] The responded message from VIS is optional descriptive error message that can include relevant ID Sent from VIS when method (POST, GET, DELETE etc) is not allowed

HTTP Code 500 The server encountered an unexpected condition which prevented it from fulfilling the request. [w3.org] The responded message from VIS is optional descriptive error message that can include relevant ID

HTTP Code 501 The responded message from VIS is The server does not support the functionality required to fulfill the request. This is the appropriate response when the server does not recognize the request method and is not capable of supporting it for any resource. [w3.org] The server either does not recognize the request method, or it lacks the ability to fulfil the request. Usually this implies future availability (e.g., a new feature of a web-service API) The responded message from VIS is optional descriptive error message Sent from VIS when method is not implemented

At the end – you could add text in black like ”Thank You !”