Merge branch 'leothelocust-golang-post'

6 years ago · 55f848ccf0
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@ -11,9 +11,6 @@ stages:
  - test
  - deploy

 before_script:
  - apt-get update -qq && apt-get install -y -qq sshpass

 test_coverage:
  stage: test
  script:
@ -25,6 +22,7 @@ deploy_prod:
  stage: deploy
  script:
    - echo "Deploying to Production"
    - apt-get update -qq && apt-get install -y -qq sshpass
    - npm install
    - sshpass -V
    - export SSHPASS=$SSH_PASS
--- a/posts/basic-http-routing-in-golang.html
+++ b/posts/basic-http-routing-in-golang.html
@ -0,0 +1,179 @@
 <h1 id="basic-http-routing-in-golang">Basic HTTP Routing in Golang</h1>
 <p>Golang is incredibly powerful. Its standard library has so much to offer, but I think other languages have encouraged the
    use of external libraries for even the most basic tasks. For example, with JavaScript, most inexperienced developers
    seem to use jQuery to do simple tasks like selecting an element and replacing its contents. When you and I both know
    jQuery is way overkill for such a task.
    <a href="/coming-soon">See my article on Vanilla JS basics.</a>.</p>
 <p>I believe that in order to be considered an expert in a language, you must at least be able to demonstrate using the core
    language to achieve your goal. In our current case, HTTP routing. Now to be clear, I don't think you need to write everything
    from scratch all the time, but you should have a firm grasp on what is available by the core language, and when you are
    better suited to use an external library. If you are looking for more advanced HTTP routing, then I would suggest using
    something like
    <a href="https://github.com/gin-gonic/gin">gin</a>.</p>
 <p>Enough ranting, let's get to it.</p>
 <h2 id="assumptions">Assumptions</h2>
 <p>I assume you have basic knowledge of the Go language at this point, so if not, it might be worth searching for some entry
    level basics first. See
    <a href="https://tour.golang.org">A Tour of Go</a>.</p>
 <h2 id="lets-begin">Let's begin</h2>
 <h3 id="step-1">Step 1</h3>
 <p>Here is our basic folder structure for this basic http routing example:</p>
 <pre><code>    basic-http-routing-in-golang/
        main.go
 </code></pre>
 <p>As a starting point our
    <code>main.go</code> file looks like this:</p>
 <pre><code>    package main

    import (
        &quot;fmt&quot;
        _ &quot;net/http&quot;
    )

    func main() {
        fmt.Println(&quot;Hello HTTP&quot;)
    }
 </code></pre>
 <h3 id="step-2">Step 2</h3>
 <p>Now starting at a very basic level, we can leverage the
    <a href="https://golang.org/pkg/net/http/#HandleFunc">
        <code>http.HandleFunc</code>
    </a> method.</p>
 <p>It is very simple to use and its signature is easy to understand.</p>
 <pre><code>    func HandleFunc(pattern string, handler func(ResponseWriter, *Request))
 </code></pre>
 <p>Which basically means,
    <code>http.HandleFunc(&quot;/url&quot;, routingFunction)</code> where
    <code>routingFunction</code> looks like this:</p>
 <pre><code>    func routingFunction(w http.ResponseWriter, req *http.Request) {
        fmt.Fprint(w, &quot;Hello HTTP&quot;)
    }
 </code></pre>
 <p>With
    <code>fmt.Fprint()</code> we can pass an
    <code>http.ResponseWriter</code> and a message to display. Our browser will now look like this when we visit the
    <code>/url</code> endpoint.</p>
 <p>
    <img src="file:///c%3A/Users/lolson/Projects/dev/levi/step2-browser-output.png" alt="Browser Output for Step 2 - Hellp HTTP">
 </p>
 <p>Here is what
    <code>main.go</code> looks like at this point:</p>
 <pre><code>    package main

    import (
        &quot;fmt&quot;
        &quot;log&quot;
        &quot;net/http&quot;
    )

    func main() {
        http.HandleFunc(&quot;/hello&quot;, helloHTTP)
        log.Fatal(http.ListenAndServe(&quot;:8080&quot;, nil))
    }

    func helloHTTP(w http.ResponseWriter, req *http.Request) {
        fmt.Fprint(w, &quot;Hello HTTP&quot;)
    }
 </code></pre>
 <p>Now we could stop there, as this is a &quot;basic&quot; http routing example, but I think it isn't quite useful as an example
    yet, until we start to see something slightly more practical.</p>
 <h3 id="step-3">Step 3</h3>
 <p>For starters, let's add a
    <code>NotFound</code> page when we don't match a pattern in
    <code>HandleFunc</code>.</p>
 <p>Here is what
    <code>main.go</code> looks like after that:</p>
 <pre><code>    package main

    import (
        &quot;fmt&quot;
        &quot;log&quot;
        &quot;net/http&quot;
    )

    func main() {
        http.HandleFunc(&quot;/hello&quot;, helloHTTP)
        http.HandleFunc(&quot;/&quot;, notFound)
        log.Fatal(http.ListenAndServe(&quot;:8080&quot;, nil))
    }

    func helloHTTP(w http.ResponseWriter, req *http.Request) {
        fmt.Fprint(w, &quot;Hello HTTP&quot;)
    }

    func notFound(w http.ResponseWriter, req *http.Request) {
        http.NotFound(w, req)
    }
 </code></pre>
 <p>This will match
    <code>/hello</code> and use the
    <code>HelloHTTP</code> method to print &quot;Hello HTTP&quot; to the browser. Any other urls will get caught by the
    <code>/</code> pattern and be given the
    <code>http.NotFound</code> response to the browser.</p>
 <p>So that works, but I think we can go further.</p>
 <h3 id="step-4">Step 4</h3>
 <p>We need to give ourselves something more specific than the simple contrived
    <code>/hello</code> endpoint above. So let's assume we are needing to get a user profile and we will use the url
    <code>/user/:id</code> where
    <code>:id</code> is an identifier used to get the user profile from our persistance layer (i.e. our database).</p>
 <p>We'll start by creating a new method for this GET request called
    <code>userProfile</code>:</p>
 <pre><code>    func userProfile(w http.ResponseWriter, req *http.Request) {
        userID := req.URL.Path[len(&quot;/user/&quot;):]
        fmt.Fprintf(w, &quot;User Profile: %q&quot;, userID)
    }
 </code></pre>
 <p>Notice that we get the URL from the
    <code>req</code> variable and we treat the string returned from
    <code>req.URL.Path</code> as a byte slice to get everything after the
    <code>/user/</code> in the string.
    <strong>Note: this isn't fool proof,
        <code>/user/10/ok</code> would get matched here, and we would be assigning
        <code>userID</code> to
        <code>&quot;10/ok&quot;</code>.</strong>
 </p>
 <p>And we'll add the new route in our
    <code>main</code> function:</p>
 <pre><code>    func main() {
        http.HandleFunc(&quot;/hello&quot;, helloHTTP)
        http.HandleFunc(&quot;/user/&quot;, userProfile)
        http.HandleFunc(&quot;/&quot;, notFound)
        log.Fatal(http.ListenAndServe(&quot;:8080&quot;, nil))
    }
 </code></pre>
 <p>
    <em>Note: that this pattern
        <code>/user/</code> matches the trailing
        <code>/</code> so that a call to
        <code>/user</code> in the browser would return a
        <code>404 Not Found</code>.</em>
 </p>
 <h3 id="step-5">Step 5</h3>
 <p>Ok, so we have introduced some pretty severe holes in the security of our new HTTP router. As mentioned in a note above,
    treating the
    <code>req.URL.Path</code> as a byte slice and just taking the last half is a terrible idea. So let's fix this:</p>
 <pre><code>    var validPath = regexp.MustCompile(&quot;^/(user)/([0-9]+)$&quot;)

    func getID(w http.ResponseWriter, req *http.Request) (string, error) {
        m := validPath.FindStringSubmatch(req.URL.Path)
        if m == nil {
            http.NotFound(w, req)
            return &quot;&quot;, errors.New(&quot;Invalid ID&quot;)
        }
        return m[2], nil // The ID is the second subexpression.
    }
 </code></pre>
 <p>Now we can use this method in our code:</p>
 <pre><code>    func userProfile(w http.ResponseWriter, req *http.Request) {
        userID, err := getID(w, req)
        if err != nil {
            return
        }
        fmt.Fprintf(w, &quot;User Profile: %q&quot;, userID)
    }
 </code></pre>
 <h2 id="conclusion">Conclusion</h2>
 <p>For now, I'm calling this &quot;Basic HTTP Routing in Golang&quot; article finished. But I do plan to add more as time allows.
    Additionally, I'd like to create a more advanced article that discusses the ability to respond to POST, PUT, and DELETE
    requests. Look for an &quot;Advanced HTTP routing in Golang&quot; article in the future. Thanks for reading this far.
    I wish you well in your Go endeavors.</p>
--- a/posts/basic-http-routing-in-golang.json
+++ b/posts/basic-http-routing-in-golang.json
@ -0,0 +1,9 @@
 {
    "title": "Basic HTTP Routing in Golang - Levi Olson",
    "permalink": "/posts/basic-http-routing-in-golang",
    "created_at": "2018-05-09T11:52:50-06:00",
    "created_at_short": "2018-05-09",
    "post_title": "basic http routing in golang",
    "active": "posts",
    "content_file": "basic-http-routing-in-golang.html"
 }
--- a/posts/basic-http-routing-in-golang.md
+++ b/posts/basic-http-routing-in-golang.md
@ -0,0 +1,160 @@
 # Basic HTTP Routing in Golang

 Golang is incredibly powerful.  Its standard library has so much to offer, but I think other languages have encouraged the use of external libraries for even the most basic tasks.  For example, with JavaScript, most inexperienced developers seem to use jQuery to do simple tasks like selecting an element and replacing its contents. When you and I both know jQuery is way overkill for such a task.  [See my article on Vanilla JS basics.](/coming-soon).

 I believe that in order to be considered an expert in a language, you must at least be able to demonstrate using the core language to achieve your goal.  In our current case, HTTP routing.  Now to be clear, I don't think you need to write everything from scratch all the time, but you should have a firm grasp on what is available by the core language, and when you are better suited to use an external library.  If you are looking for more advanced HTTP routing, then I would suggest using something like [gin](https://github.com/gin-gonic/gin).

 Enough ranting, let's get to it.

 ## Assumptions

 I assume you have basic knowledge of the Go language at this point, so if not, it might be worth searching for some entry level basics first.  See [A Tour of Go](https://tour.golang.org).

 ## Let's begin

 The accompanying repo for the code produced in this article is located [on github](https://github.com/leothelocust/basic-http-routing-in-golang).

 ### Step 1

 Here is our basic folder structure for this basic http routing example:

        basic-http-routing-in-golang/
            main.go

 As a starting point our `main.go` file looks like this:

        package main

        import (
            "fmt"
            _ "net/http"
        )

        func main() {
            fmt.Println("Hello HTTP")
        }

 ### Step 2

 Now starting at a very basic level, we can leverage the [`http.HandleFunc`](https://golang.org/pkg/net/http/#HandleFunc) method.

 It is very simple to use and its signature is easy to understand.

        func HandleFunc(pattern string, handler func(ResponseWriter, *Request))

 Which basically means, `http.HandleFunc("/url", routingFunction)` where `routingFunction` looks like this:

        func routingFunction(w http.ResponseWriter, req *http.Request) {
            fmt.Fprint(w, "Hello HTTP")
        }

 With `fmt.Fprint()` we can pass an `http.ResponseWriter` and a message to display.  Our browser will now look like this when we visit the `/url` endpoint.

 ![Browser Output for Step 2 - Hellp HTTP](step2-browser-output.png)

 Here is what `main.go` looks like at this point:

        package main

        import (
            "fmt"
            "log"
            "net/http"
        )

        func main() {
            http.HandleFunc("/hello", helloHTTP)
            log.Fatal(http.ListenAndServe(":8080", nil))
        }

        func helloHTTP(w http.ResponseWriter, req *http.Request) {
            fmt.Fprint(w, "Hello HTTP")
        }

 Now we could stop there, as this is a "basic" http routing example, but I think it isn't quite useful as an example yet, until we start to see something slightly more practical.

 ### Step 3

 For starters, let's add a `NotFound` page when we don't match a pattern in `HandleFunc`.

 Here is what `main.go` looks like after that:

        package main

        import (
            "fmt"
            "log"
            "net/http"
        )

        func main() {
            http.HandleFunc("/hello", helloHTTP)
            http.HandleFunc("/", notFound)
            log.Fatal(http.ListenAndServe(":8080", nil))
        }

        func helloHTTP(w http.ResponseWriter, req *http.Request) {
            fmt.Fprint(w, "Hello HTTP")
        }

        func notFound(w http.ResponseWriter, req *http.Request) {
            http.NotFound(w, req)
        }

 This will match `/hello` and use the `HelloHTTP` method to print "Hello HTTP" to the browser.  Any other urls will get caught by the `/` pattern and be given the `http.NotFound` response to the browser.

 So that works, but I think we can go further.

 ### Step 4

 We need to give ourselves something more specific than the simple contrived `/hello` endpoint above.  So let's assume we are needing to get a user profile and we will use the url `/user/:id` where `:id` is an identifier used to get the user profile from our persistance layer (i.e. our database).

 We'll start by creating a new method for this GET request called `userProfile`:

        func userProfile(w http.ResponseWriter, req *http.Request) {
            userID := req.URL.Path[len("/user/"):]
            fmt.Fprintf(w, "User Profile: %q", userID)
        }

 Notice that we get the URL from the `req` variable and we treat the string returned from `req.URL.Path` as a byte slice to get everything after the `/user/` in the string.  **Note: this isn't fool proof, `/user/10/ok` would get matched here, and we would be assigning `userID` to `"10/ok"`.**

 And we'll add the new route in our `main` function:

        func main() {
            http.HandleFunc("/hello", helloHTTP)
            http.HandleFunc("/user/", userProfile)
            http.HandleFunc("/", notFound)
            log.Fatal(http.ListenAndServe(":8080", nil))
        }

 _Note: that this pattern `/user/` matches the trailing `/` so that a call to `/user` in the browser would return a `404 Not Found`._


 ### Step 5

 Ok, so we have introduced some pretty severe holes in the security of our new HTTP router.  As mentioned in a note above, treating the `req.URL.Path` as a byte slice and just taking the last half is a terrible idea.  So let's fix this:

        var validPath = regexp.MustCompile("^/(user)/([0-9]+)$")

        func getID(w http.ResponseWriter, req *http.Request) (string, error) {
            m := validPath.FindStringSubmatch(req.URL.Path)
            if m == nil {
                http.NotFound(w, req)
                return "", errors.New("Invalid ID")
            }
            return m[2], nil // The ID is the second subexpression.
        }

 Now we can use this method in our code:

        func userProfile(w http.ResponseWriter, req *http.Request) {
            userID, err := getID(w, req)
            if err != nil {
                return
            }
            fmt.Fprintf(w, "User Profile: %q", userID)
        }

 ## Conclusion

 For now, I'm calling this "Basic HTTP Routing in Golang" article finished.  But I do plan to add more as time allows.  Additionally, I'd like to create a more advanced article that discusses the ability to respond to POST, PUT, and DELETE requests.  Look for an "Advanced HTTP routing in Golang" article in the future.  Thanks for reading this far.  I wish you well in your Go endeavors.
--- a/posts/step2-browser-output.png
+++ b/posts/step2-browser-output.png