# Jersey WebResource - Header don't get appended

DevFeed: [Jersey WebResource - Header don't get appended](<https://devfeed.tech/articles/jersey-webresource-header-don-t-get-appended-21241.md>)

Original publisher: [Read original article](<https://juri.dev/blog/2015/05/jersey-webresource-ignores-headers/>)

Published: 2015-05-13T00:00:00Z

Content type: tutorial

Language: en

Sources: [Juri Strumpflohner](<https://devfeed.tech/sources/juri-strumpflohner.md>)

Topics: [Java](<https://devfeed.tech/topics/java.md>), [REST API](<https://devfeed.tech/topics/rest-api.md>), [HTTP](<https://devfeed.tech/topics/http.md>), [Authentication](<https://devfeed.tech/topics/authentication.md>), [Authorization](<https://devfeed.tech/topics/authorization.md>)

Tags: [authentication](<https://devfeed.tech/tags/authentication.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [http](<https://devfeed.tech/tags/http.md>), [java](<https://devfeed.tech/tags/java.md>), [logging](<https://devfeed.tech/tags/logging.md>), [rest](<https://devfeed.tech/tags/rest.md>), [rest-api](<https://devfeed.tech/tags/rest-api.md>)

## AI overview

This article explains why headers added through Jersey's WebResource API were ignored. It shows that calls on the original WebResource create new Builder objects, so headers must be added to the returned builder instance before executing the HTTP request.

## Source excerpt

Lorem ipsum dolor sit amet