I can't because I can't really replicate being run on a heroku dyno.
However, any rest method that you can set on a heroku dyno and then access
the URL using HTTPS will recreate the issue. Just use an @Context UriInfo
info in any GET method and inspect the info.getBaseUri(). If you accessed
the end-point via heroku and using the HTTPS scheme you should see port 80
there. If you switch to Jetty you will see no port specified.
On Wed, Mar 12, 2014 at 7:04 PM, Oleksiy Stashok <oleksiy.stashok_at_oracle.com
> wrote:
>
> On 12.03.14 15:55, Robert DiFalco wrote:
>
> Ah yes, then I can't say for sure if it is a bug or not. But heroku is
> forwarding https without a port to 443. So if the BaseURI/Request does not
> specify a port and it is used for a redirect then there is no problem. But
> if it has an 80 shoved in there then the redirect URI will be broken
> because https cannot go through 80 from the client. Make sense?
>
> Do you have a testcase to reproduce the problem?
>
> Thanks.
>
> WBR,
> Alexey.
>
>
> I can see the rational for both approaches. It's just weird that Jetty
> and Grizzly work differently and I have to code accordingly.
>
>
> On Wed, Mar 12, 2014 at 3:48 PM, Oleksiy Stashok <
> oleksiy.stashok_at_oracle.com> wrote:
>
>>
>> On 12.03.14 15:30, Robert DiFalco wrote:
>>
>> 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).
>>
>> AFAIR In HTTP URL if you don't specify the port - port 80 is implied. So
>> HTTP URL with and without port 80 refer to the same resource.
>>
>> WBR,
>> Alexey.
>>
>>
>>
>> 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?
>>>>
>>>>
>>>>
>>>
>>
>>
>
>