glassfish_at_javadesktop.org wrote:
> Sorry I figured this out, very basic mistake.
>
> How can I delete or remove a posting like this?
Your post is still important :-) I suspect port 81 was using SSL (one of
the port), right? Issuing a clean request on an SSL port in Java always
create the behavior your have experienced, e.g. you connection loops
forever (the reverse is true as well). All Java Web Server will suffer
the same problem.
Fortunately for GlassFish :-), we have a mechanism that allow sending
http requests to secure/ssl port [1] and vice versa (the mechanism allow
supporting more that one transport using one port).
What you can do is edit your http-listener using admin cli or gui, and
add the following property under your http-listener port="81"
<property name="proxiedProtocols" value="http"/>
Save. Now doing:
http://1.2.3.4:81/getStuff
and
https://1.2.3.4:81/getStuff
will both works. Note that the reverse works as well. You can define the
http-listener port=80 with:
<property name="proxiedProtocols" value="tls"/> and now:
http://1.2.3.4:80/getStuff
and
https://1.2.3.4:80/getStuff
will both works.
-- Jeanfrancois
[1]
http://weblogs.java.net/blog/jfarcand/archive/2006/11/one_port_to_rul.html
>
> S.D.
> [Message sent by forum member 'samdoyle' (samdoyle)]
>
> http://forums.java.net/jive/thread.jspa?messageID=247427
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>