Problem's root cause was elsewhere, as always :)
Ari Heino wrote:
>
> Hi!
>
> I noticed when using Jersey (1.0.3.1) UriInfo:
>
> @Context private final UriInfo uriInfo;
> .
> .
> .
> String path = uriInfo.getAbsolutePath().toString();
>
> That the domain segment of the URI is actually dependent on the incoming
> request. So if server receives 2 requests:
>
> http://localhost:8080/webservices
> http://127.0.0.1:8080/webservices
>
> then the output of the "path" string is different even if it is actually
> exactly same server that is sending the response.
>
> So my question is, is there a way to get server's domain segment of the
> URI with Jersey framework? Or is it available via some servlet framework
> or something?
>
> Cheers,
>
> .aRi
>
>
--
View this message in context: http://n2.nabble.com/Resolving-server-s-URI-tp3911181p3911956.html
Sent from the Jersey mailing list archive at Nabble.com.