Shulou(Shulou.com)06/01 Report--

Today, I will talk to you about how to understand the static resource response of route matching based on gorilla/mux packets. Many people may not know much about it. In order to make you understand better, the editor summarizes the following contents. I hope you can get something from this article.

So far, we have been dealing with dynamic resources, that is, responses implemented by Go code. In addition to dealing with dynamic resources, HTTP servers should also have the ability to deal with static resources, such as HTML, CSS, JavaScript, and pictures all belong to the category of static resources.

To deal with static resources, you need to specify the path prefix where the static resources are located with the help of the PathPrefix () method, and then return the file content itself directly in the request processor as a response through http.FileServer:

Func main () {r: = mux.NewRouter () r.Use (loggingMiddleware)

/ / parse server startup parameter dir as static resource Web root directory / / default is the current directory. Var dir string flag.StringVar (& dir, "dir", ".", "directory where static resources are located, default is current directory") flag.Parse ()

/ / handle static resource routes such as http://localhost:8000/static/ r.PathPrefix ("/ static/") .Handler (http.StripPrefix ("/ static/", http.FileServer (http.Dir (dir) / / other routes. Log.Fatal (http.ListenAndServe (": 8080", r))}

Taking the above code as an example, when we request a http://localhost:8080/static/app.js file, we look for app.js in the static directory and return 404 if it is not found, otherwise the file itself is returned as a response.

Let's try to create a static/app.js in the same directory as the above entry file, and the initialization code is as follows:

[xss_clean] ("hello from javascript")

Then place a picture test.jpg file in the static directory and start the HTTP server:

Go run mux.go-dir=static

Note that we specify that the root directory of the static resource is static through the dir parameter, and accessing the static resource will report 404 if not specified.

Next, you can access the static resources in the server's static directory in the browser:

Although the gorilla/mux router provides support for static resources, we usually deal with static resources based on Nginx, just like PHP, and then forward dynamic requests to Go HTTP servers, because Nginx, as a powerful reverse proxy server, has a strong ability to handle static resources concurrently, so there is no need to deal with this logic ourselves.

After reading the above, do you have any further understanding of how to deal with static resource responses based on gorilla/mux packets for route matching? If you want to know more knowledge or related content, please follow the industry information channel, thank you for your support.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.