We fixed the issue
http://java.net/jira/browse/GRIZZLY-1264
so 400 Bad Request status will be returned during the initial request
parsing and not even reach Jersey code.
According to the comment on stackoverflow, the fixed request may look like:
|GET
https://servername:9960/ HTTP/1.1\r\nHost:\r\nConnection: close\r\n\r\n
|
The Host header is ignored (according to the HTTP spec) if the requested
URI is absolute.
WBR,
Alexey.
On 05/16/2012 10:40 AM, Oleksiy Stashok wrote:
> forwarding to grizzly mailing list.
>
>
>
> -------- Original Message --------
> Subject: Re: [Jersey] Fwd: Re: Strange Exception on Linux
> java.lang.IllegalArgumentException: java.net.URISyntaxException:
> Expected hostname at index 8: https://:443/
> Date: Wed, 16 May 2012 05:37:10 +0000 (GMT)
> From: <mbuesch_at_gmail.com>
> To: oleksiy.stashok_at_oracle.com
>
>
>
> Hi
> The detail for the request could be found here
> http://java.net/projects/jersey/lists/users/archive/2012-05/message/31
> and here
> http://stackoverflow.com/questions/10487594/jersey-grizzly-restful-serv
> er-throws-a-strange-urisyntaxexception-on-linux
>
> Thanks for your answer.
> Regards,
> Marcel