kedar wrote:
> It was available only on the enterprise profile domain by default.
That is not what I ran into in testing, yesterday.
Here is the test that I did...
1. java -jar the v2.1 jar.
2. ant -f setup.xml
3. start the default domain
4. open the admin gui
5. use the admin gui to change the 'security' flag on the admin listener.
6. restart the server.
7. use
http://localhost:4848 to reconnect with the admin listener on the
restarted server
the redirect happened, with no additional configuration...
> Otherwise
> you had to add a property (proxiedProtocols) by hand. Since we don't have
> an enterprise profile domain in v3 yet, technically, this ability has to
> reappear in v3 ;)
Ummm...
>
> But I understand what you mean. You just want http://host:admin-port to
> redirect to https://host:admin-port if admin-listener is secure on given
> host and port. Makes sense.
>
> JF -- How should this be done on Grizzly 1.9.18+? I believe this has
> changed
> from Grizzly 1.0.x (v2), right?
>
> -Kedar
>
> vince kraemer wrote:
>> Hi all,
>>
>> back in the v2 timeframe, I think I remember being able to type
>> http://localhost:4848 into the browser's address field... even when
>> the server had security enabled on the admin-listener...
>>
>> The server would do a redirect to get the browser to speak https.
>>
>> It seems like that feature went away with v3.
>>
>> Or has senility set in???
>>
>> Thanks,
>> vbk