Certificate Associate in Web Development – Request-Response cycle
Before we start building web applications or web servers, it’s a good idea to understand the basics of how they work. What is HTTP? What is a request and a response? What does it look like? These are some of the questions that will be answered in this course. To reinforce the concepts, we will try to go through the steps of what happens when a user types a URL in the browser.
Whenever our Web browser tries communicating with a Web server, it is done by using the Hypertext Transfer Protocol (HTTP) which functions as a request-response protocol. In this process of communication, we send a request to the web server and expect a response in return.
When a user goes to the browser and types a URL, what exactly is happening?
A Requests object is the one which is created by the user when he/she tries to interact with a web resource. It will be sent as a prepared request to the server and does contain some parameters which are optional.
A Response object contains the response of the server to a HTTP request. It is generated once Requests gets a response back from the server. It contains all of the information returned by the server and also stores the Request object we created originally.
With the HTTP protocol, the client makes a request to the server. This request is answered with a response. The request consists of a header and, in many cases, body information to the server. The server uses the body information to define different results based on the needs of the client. Let’s have a look at what information can be read from the client.
Whenever we make a call to a server using the requests, two major transactions are taking place in this context which are listed as follows:
We are constructing a Request object which will be sent out to the server to request a resource
A Response object is generated by the requests module
Upon completion of the course, participants should be able to:
- Understand how to make a simple request, different types of response content, adding custom headers to our requests
- Dealing with form encoded data, using the status code lookup, locating the request redirection, location, and timeouts
- Using session objects, Understand structure of request and response, prepared Requests, SSL verification with Requests, streaming uploads, generators, and event hooks
- Using proxies, link headers, and transport headers
- Understand different types of procedures that are in practice for authentication
- Mocking HTTP Requests using Postman
- Interacting with Social Media Using Requests
Who should attend
This course will help beginners, programmers, application developers and software engineers pick the right strategy for developing cross-platform web applications that run on a variety of desktop computers as well as mobile devices. The primary audience is developers who need to learn how to develop web applications using the HTML5 stack.
Foundational certificate in Programming
Mix of Instructor-led, case study driven and hands-on for select phases
H/w, S/w Reqd
24 Hours (2 days Instructor led + 8 hours online learning)
- Course Name:Certificate Associate in Web Development – Request-Response cycle
- Duration:2 days classroom + 8 hours online
- Exam Time: 60 minutes
- Course Price: Call for price
- Minimum requirements: Foundational Certificate in Programming
|#||Topic||Method of Delivery|
Interacting with the Web Using Requests
Introduction to HTTP request
Essence of Requests
Making a simple request
Different types of request contents
Looking up built-in response status codes
Viewing response headers
Accessing cookies with Requests
Tracking redirection of the request using request history
Using timeout to keep productive usage in check
Errors and exceptions
Persisting parameters across Requests using Session objects
Revealing the structure of a request and response
Using prepared Requests
Verifying an SSL certificate with Requests
Body Content Workflow
Using generator for sending chunk encoded Requests
Getting the request method arguments with event hooks
Iterating over streaming APIs
Self-describing the APIs with link headers
Working with Postman
|Online Self paced|
- Certificate Associate in Web Development – Request-Response Cycle
- Certificate Awarding Body: ITPACS
Information Technology Professional Accreditations and Certifications Society (ITPACS) is a non-profit organization focused on improving technology skills for the future. ITPACS offers associate level, professional level and leader certifications across 6 domains including data science, web development, mobile development, cyber security, IoT and blockchain. Applicants have to go through a exam eligibility process demonstrating their experience.
The Associate certification is catered to individuals with less than 1 year working experience in the field. This is ideal for newcomers starting out in the profession or those seeking to make an entry into the profession. Applicants are required to have completed the application process prior to taking the exam.
- Exam Format: Closed-book format.
Questions: 30 multiple choice questions, coding exercises
Passing Score: 65%
Exam Duration: 60 minutes
- Exam needs to be taken within 12 months from the exam voucher issue date
Web Developers build web applications. A web application is one that helps an organization run its business online. Most web applications are built in a three-tier architecture that consists of three important layers: data, logic, and presentation. In web applications, the application structure usually breaks down to database, server, and client, while in modern web development; it can also be broken into database, server logic, client logic, and client UI.
Dynamic web pages are known as pages that are created as soon as a call is sent to the server. So data can be built interactively into the sites. They are particularly helpful when you need to react to user inputs. Forms can be evaluated immediately and the content of the next page can be shown. The application possibilities are nearly unlimited. Whether and to which extent databases are used depends on the goal. Dynamic web pages actually do not need a database.
A popular paradigm for implementing this model is the Model-View-Controller (MVC) architectural pattern. In the MVC paradigm, the logic, data, and visualization are separated into three types of object, each handling its own tasks. The View handles the visual part, taking care of user interaction. The Controller responds to system and user events, commanding the Model and View to change appropriately. The Model handles data manipulation, responding to requests for information or changing its state according to the Controller’s instructions.