How do I handle JSON requests and responses in gocraft/web?

gocraft/web doesn't include built-in JSON binding. You'll need to write custom middleware to parse JSON requests and serialize responses, or use community extensions like the linked json-binding package.

gocraft/web vs gorilla/mux: which is better for my project?

gocraft/web offers better performance with O(log(N)) routing and static typing via contexts, while gorilla/mux has a simpler API and broader ecosystem. Choose gocraft/web for type safety and scalability, gorilla/mux for ease of use.

How to implement authentication middleware with sessions?

Create a custom middleware that reads session cookies, sets user data in the context struct, and calls next() only if authenticated. The README provides an example with UserRequired middleware for guidance.

Does gocraft/web support middleware that runs after the handler?

Yes, by placing code after the next() call in middleware, you can execute logic during the unwind phase, such as logging response times or cleaning up resources.

How to handle CORS in gocraft/web?

Implement custom middleware to set CORS headers, or use the built-in OPTIONS handler to automatically allow methods. The README shows an example OPTIONS handler for adding Access-Control-Allow-Origin headers.

Can I use gocraft/web with Go modules and newer Go versions?

Yes, it's compatible with Go modules, but note that the library hasn't seen major updates recently, so check for community forks or ensure it works with your Go version for long-term support.

web — Go Mux & Middleware Package

What is web?

gocraft/web is a Go router and middleware package for building web applications. It provides a fast, tree-based router with O(log(N)) routing performance and emphasizes type safety through custom contexts, allowing developers to pass strongly typed data between middleware and handlers.

Target Audience

Go developers building web applications who need a performant, type-safe router with flexible middleware composition and nested routing capabilities.

Value Proposition

Developers choose gocraft/web for its combination of high performance (adding as little as 3-10μs latency), static typing via custom contexts, and a clean API that integrates seamlessly with Go's standard net/http package.

Go Router + Middleware. Your Contexts.

Use Cases

Best For

Building web applications where type safety and performance are critical, such as high-traffic APIs or services.
Creating hierarchical web applications with distinct sections (e.g., admin areas, API routes) that require different middleware and context structures.
Implementing middleware chains that need to pass strongly typed data (like user sessions or access tokens) between handlers.
Developing applications with many routes where O(log(N)) routing scalability is necessary to maintain low latency.
Integrating with existing Go net/http ecosystems while adding structured routing and middleware features.
Handling complex routing needs with path parameter capture, regex validation, and wildcard matching.

Not Ideal For

Projects requiring built-in HTTP/2 or WebSocket support without additional middleware
Teams that prefer full-stack frameworks with integrated templating, ORM, and auto-generated API docs
Applications where optional path segments are critical, as it requires defining multiple routes manually

Pros & Cons

Pros

Blazing Fast Performance

Benchmarks show added latency of only 3-10μs per request with O(log(N)) routing scalability, as tracked in BENCHMARK_RESULTS, ensuring low overhead for high-traffic apps.

Statically Typed Contexts

Enables passing strongly typed data between middleware and handlers using custom structs, improving code safety and reducing runtime errors compared to dynamic maps.

Flexible Nested Routers

Supports hierarchical routing with different contexts and middleware for distinct app sections, like admin areas or APIs, allowing clean separation of concerns.

Seamless net/http Integration

Works directly with Go's standard http package, including http.ResponseWriter and http.Request, making it easy to integrate into existing Go ecosystems.

Cons

Limited Path Parameter Flexibility

Does not support optional path segments or regexps outside segments, requiring multiple route definitions for variations, as admitted in the README.

Sparse Built-in Middleware

Ships with only basic middleware (logger, error show, static files), forcing reliance on community contributions or custom code for advanced features like JSON binding.

Complex Context Hierarchy

Nested routers require careful embedding of parent contexts in structs, which can lead to boilerplate and increased cognitive load for setup and maintenance.

Frequently Asked Questions

What is web?

Target Audience

Go developers building web applications who need a performant, type-safe router with flexible middleware composition and nested routing capabilities.

Value Proposition

Use Cases

Best For

Building web applications where type safety and performance are critical, such as high-traffic APIs or services.
Creating hierarchical web applications with distinct sections (e.g., admin areas, API routes) that require different middleware and context structures.
Implementing middleware chains that need to pass strongly typed data (like user sessions or access tokens) between handlers.
Developing applications with many routes where O(log(N)) routing scalability is necessary to maintain low latency.
Integrating with existing Go net/http ecosystems while adding structured routing and middleware features.
Handling complex routing needs with path parameter capture, regex validation, and wildcard matching.

Not Ideal For

Projects requiring built-in HTTP/2 or WebSocket support without additional middleware
Teams that prefer full-stack frameworks with integrated templating, ORM, and auto-generated API docs
Applications where optional path segments are critical, as it requires defining multiple routes manually

Pros & Cons

Pros

Blazing Fast Performance

Benchmarks show added latency of only 3-10μs per request with O(log(N)) routing scalability, as tracked in BENCHMARK_RESULTS, ensuring low overhead for high-traffic apps.

Statically Typed Contexts

Enables passing strongly typed data between middleware and handlers using custom structs, improving code safety and reducing runtime errors compared to dynamic maps.

Flexible Nested Routers

Supports hierarchical routing with different contexts and middleware for distinct app sections, like admin areas or APIs, allowing clean separation of concerns.

Seamless net/http Integration

Works directly with Go's standard http package, including http.ResponseWriter and http.Request, making it easy to integrate into existing Go ecosystems.

Cons

Limited Path Parameter Flexibility

Does not support optional path segments or regexps outside segments, requiring multiple route definitions for variations, as admitted in the README.

Sparse Built-in Middleware

Ships with only basic middleware (logger, error show, static files), forcing reliance on community contributions or custom code for advanced features like JSON binding.

Complex Context Hierarchy

Nested routers require careful embedding of parent contexts in structs, which can lead to boilerplate and increased cognitive load for setup and maintenance.

Frequently Asked Questions

web

What is web?

Overview

Use Cases

Best For

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions

Related Projects

Found a gem we're missing?

web

What is web?

Overview

Use Cases

Best For

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions

Related Projects

Found a gem we're missing?