Tips and Tricks

Leveraging the HTTP Header Location

There's more to RESTful services than just using the HTTP verbs. You should also be leveraging the Location header and status code, for example.

When REST was proposed as a way of leveraging the HTTP protocol, the idea was to do more than just take advantage of the HTTP verbs GET, POST, DELETE and so on -- the goal was to take advantage of all the features of HTTP. If you're creating RESTful services, you should be following that paradigm.

For example, HTTP headers can include a status code that indicates a new resource was created and a URL that points to that resource. In a RESTful application, if you add a new customer, then you should be sending the client a message with headers that include the HTTP Created status code and a Location set to the URL where the new customer could be retrieved. The code to create those headers would look something like this:

Public Function CreateCustomer(cust As Customer) As ActionResult
  Dim newCust As Customer
  '... code to add a customer with Id of 'A123'... 
  Response.StatusCode = HttpStatusCode.Created
  Dim hlpr As New UrlHelper(ControllerContext.RequestContext)
  Response.AppendHeader(
    "Location", hlpr.Action("GetCustomer", "Customer", New With {.id = "A123"}))     
End Function

The client can now check the HTTP status code and, when the client discovers that Created status, use the Location header to find the new resource. It's the RESTful way to do it.

About the Author

Peter Vogel is a system architect and principal in PH&V Information Services. PH&V provides full-stack consulting from UX design through object modeling to database design. Peter tweets about his VSM columns with the hashtag #vogelarticles. His blog posts on user experience design can be found at http://blog.learningtree.com/tag/ui/.

comments powered by Disqus

Featured

  • Spring AI 2.0 Goes GA, Giving Java Developers a More Mature AI App Stack

    Spring AI 2.0 advances the Java framework for generative AI apps with a Spring Boot 4 baseline, cleaner agentic tooling, Model Context Protocol support and vendor-backed integrations including Azure Cosmos DB.

  • Kubernetes for Developers

    Microsoft's Dan Wahlin previews his introductory "Kubernetes for Developers" session at Visual Studio Live! San Diego 2026, explaining how developers can get past the Kubernetes learning curve by starting locally, mastering Pods first, and using Services to make containerized applications reliably accessible.

  • VS Code Keeps Eye on Costs in v1.126 Update

    Visual Studio Code 1.126 adds session-level Copilot cost information, continuing Microsoft's recent focus on helping developers monitor and manage usage-based GitHub Copilot billing.

  • Open VSX 1.0.0 Puts Focus on Open Extension Registry for VS Code Ecosystem

    Eclipse Open VSX has reached 1.0.0, highlighting its role as a vendor-neutral registry for VS Code-compatible extensions.

Subscribe on YouTube