httpin alternatives and similar packages

Based on the "Forms" category.
Alternatively, view httpin alternatives based on common mentions on social networks and blogs.

nosurf

7.8 0.0 httpin VS nosurf

CSRF protection middleware for Go.
gorilla/csrf

7.4 1.1 httpin VS gorilla/csrf

DISCONTINUED. gorilla/csrf provides Cross Site Request Forgery (CSRF) prevention middleware for Go web applications & services 🔒

WorkOS - The modern identity platform for B2B SaaS

The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.

Promo workos.com

binding

7.3 0.0 httpin VS binding

DISCONTINUED. Reflectionless data binding for Go's net/http (not actively maintained)
form

6.8 2.8 httpin VS form

:steam_locomotive: Decodes url.Values into Go value(s) and Encodes Go value(s) into url.Values. Dual Array and Full map support.
conform

5.8 0.0 httpin VS conform

Trims, sanitizes & scrubs data based on struct tags (go, golang)
formam

5.0 0.0 httpin VS formam

a package for decode form's values into struct in Go
forms

4.8 0.0 httpin VS forms

A lightweight go library for parsing form data or json from an http.Request.
qs

3.3 4.3 httpin VS qs

Go module for encoding structs into URL query parameters
bind

2.5 0.0 httpin VS bind

Bind form data to any Go values
queryparam

2.1 0.0 httpin VS queryparam

Go package to easily convert a URL's query parameters/values into usable struct values of the correct types.
gbind

0.7 6.1 httpin VS gbind

Bind data to any Go value. Can use built-in and custom expression binding capabilities; supports data validation logic for Go values. // 将数据绑定到任何 Go 值。可使用内置和自定义表达式绑定能力；支持对Go值的数据校验逻辑.
checker

0.7 7.6 httpin VS checker

Checker is a Go library for validating user input through checker rules provided in struct tags.

Do you think we are missing an alternative of httpin or a related project?

Add another 'Forms' Package

Popular Comparisons

README

httpin - HTTP Input for Go

Decode an HTTP request into a custom struct

Documentation

Core Features

httpin helps you easily decoding HTTP request data from

Query parameters, e.g. ?name=john&is_member=true
Headers, e.g. Authorization: xxx
Form data, e.g. username=john&password=******
JSON/XML Body, e.g. POST {"name":"john"}
Path variables, e.g. /users/{username}
File uploads

You only need to define a struct to receive/bind data from an HTTP request, without writing any parsing stuff code by yourself.

How to use?

type ListUsersInput struct {
    Page     int  `in:"query=page"`
    PerPage  int  `in:"query=per_page"`
    IsMember bool `in:"query=is_member"`
}

func ListUsers(rw http.ResponseWriter, r *http.Request) {
    input := r.Context().Value(httpin.Input).(*ListUsersInput)

    if input.IsMember {
        // Do sth.
    }
    // Do sth.
}

httpin is:

well documented: at https://ggicci.github.io/httpin/
open integrated: with net/http, go-chi/chi, gorilla/mux, gin-gonic/gin, etc.
extensible (advanced feature): by adding your custom directives. Read httpin - custom directives for more details.

Why this package?

Compared with using `net/http` package

func ListUsers(rw http.ResponseWriter, r *http.Request) {
    page, err := strconv.ParseInt(r.FormValue("page"), 10, 64)
    if err != nil {
        // Invalid parameter: page.
        return
    }
    perPage, err := strconv.ParseInt(r.FormValue("per_page"), 10, 64)
    if err != nil {
        // Invalid parameter: per_page.
        return
    }
    isMember, err := strconv.ParseBool(r.FormValue("is_member"))
    if err != nil {
        // Invalid parameter: is_member.
        return
    }

    // Do sth.
}

Benefits	Before (use net/http package)	After (use ggicci/httpin package)
⌛️ Developer Time	😫 Expensive (too much parsing stuff code)	🚀 Faster (define the struct for receiving input data and leave the parsing job to httpin)
♻️ Code Repetition Rate	😞 High	😍 Lower
📖 Code Readability	😟 Poor	🤩 Highly readable
🔨 Maintainability	😡 Poor	🥰 Highly maintainable