users@jersey.java.net

[Jersey] Re: UriInfo oddness on Jetty vs Grizzly

From: Robert DiFalco <robert.difalco_at_gmail.com>
Date: Wed, 12 Mar 2014 15:30:25 -0700

Well, before we go too fast. Why does Jetty not include the port while
Grizzly does? Does it have to do with me not using a Servlet on Grizzly
while I did on Jetty? I'm not even sure between the two which is the
correct behavior (when running behind heroku).


On Wed, Mar 12, 2014 at 3:19 PM, Oleksiy Stashok <oleksiy.stashok_at_oracle.com
> wrote:

> Hi Robert,
>
> it doesn't sound like a bug, but for sure we can change that behavior.
> Please file an issue @ [1]
>
> Thanks.
>
> WBR,
> Alexey.
>
> [1] https://java.net/jira/browse/GRIZZLY
>
> On 12.03.14 12:04, Robert DiFalco wrote:
>
>> I recently changed my heroku deployed app from Jetty to Grizzly. I am now
>> getting some weird behavior.
>>
>> When I create my redirect URIs I now get a port 80 in the URI whereas
>> under Jetty I get one with no port specified. I do NOT want the port
>> specified.
>>
>> Any ideas what can be going on here?
>>
>>
>>
>