- Go: Building Web Applications
- Table of Contents
- Go: Building Web Applications
- Go: Building Web Applications
- Credits
- Preface
- 1. Module 1
- 2. Module 2
- 1. Chat Application with Web Sockets
- 2. Adding Authentication
- 3. Three Ways to Implement Profile Pictures
- 4. Command-line Tools to Find Domain Names
- 5. Building Distributed Systems and Working with Flexible Data
- 6. Exposing Data and Functionality through a RESTful Data Web Service API
- 7. Random Recommendations Web Service
- 8. Filesystem Backup
- 3. Module 3
- 1. An Introduction to Concurrency in Go
- 2. Understanding the Concurrency Model
- 3. Developing a Concurrent Strategy
- 4. Data Integrity in an Application
- 5. Locks, Blocks, and Better Channels
- 6. C10K – A Non-blocking Web Server in Go
- 7. Performance and Scalability
- 8. Concurrent Application Architecture
- Designing our concurrent application
- Identifying our requirements
- Using NoSQL as a data store in Go
- Monitoring filesystem changes
- Managing logfiles
- Handling configuration files
- Detecting file changes
- Backing up our files
- Designing our web interface
- Reverting a file's history – command line
- Checking the health of our server
- Summary
- 9. Logging and Testing Concurrency in Go
- 10. Advanced Concurrency and Best Practices
- Going beyond the basics with channels
- Building workers
- Implementing nil channel blocks
- Implementing more granular control over goroutines with tomb
- Timing out with channels
- Building a load balancer with concurrent patterns
- Choosing unidirectional and bidirectional channels
- Using an indeterminate channel type
- Using Go with unit testing
- Using Google App Engine
- Utilizing best practices
- Summary
- A. Bibliography
- Index
Before we look at simple and incredibly common errors like 404s, let's address the idea of redirecting requests, something that's very common. Although not always for reasons that are evident or tangible for the average user.
So we might we want to redirect requests to another request? Well there are quite a few reasons, as defined by the HTTP specification that could lead us to implement automatic redirects on any given request. Here are a few of them with their corresponding HTTP status codes:
- A non-canonical address may need to be redirected to the canonical one for SEO purposes or for changes in site architecture. This is handled by 301 Moved Permanently or 302 Found.
- Redirecting after a successful or unsuccessful
POST. This helps us to prevent re-POSTing of the same form data accidentally. Typically, this is defined by 307 Temporary Redirect. - The page is not necessarily missing, but it now lives in another location. This is handled by the status code 301 Moved Permanently.
Executing any one of these is incredibly simple in basic Go with net/http, but as you might expect, it is facilitated and improved with more robust frameworks, such as Gorilla.
-
No Comment
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.