I think I found the answer to my question. The secure URL I was testing against was being dynamically built from the HttpSerlvetRequest and I simply changed the http to https without changing the URL to point to the secure port. The URL was pulling the port from the request in this manner.
....request.getServerPort()... well, initially the site was accessed through the non-secure port (8080) so this was the value getting plugged into the URL...net effect is an invalid URL. https://somesite:8080/... when in fact the port should have been 8443 as in, https://somesite:8443/... J.D. <a href="http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3826230#3826230";>View the original post</a> <a href="http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3826230>Reply to the post</a> ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
