Documente Academic
Documente Profesional
Documente Cultură
U n i f i c a t i o n
i n
G l a s s F i s h
Pa r t
It's taken more time to get back to this topic but it's time. In part 1, I covered how to set up GlassFish to push all HTTP traffic to HTTPS. In this post,
I'll show you how to set up the reverse. In the next post, I'll cover how to configure GlassFish to serve up multiple protocols from the same port. The
steps are basically the same so this will be a short one. Similar to last time, we'll issue a few simple commands:
asadmin create-protocol --securityenabled=true https-redirect
asadmin create-protocol-filter --protocol https-redirect --classname com.sun.grizzly.config.HttpRedirectFilter
redirect-filter
asadmin create-ssl --certname s1as --type network-listener --ssl2enabled false --ssl3enabled false -clientauthenabled false https-redirect
asadmin create-protocol pu-protocol
asadmin create-protocol-finder --protocol
com.sun.grizzly.config.HttpProtocolFinder
asadmin create-protocol-finder --protocol
com.sun.grizzly.config.HttpProtocolFinder
converted by W eb2PDFConvert.com
Content-Type: text/html
Content-Length: 5212
Date: Fri, 23 Jul 2010 16:57:31 GMT
Connection: Keep-Alive
That's it. As promised, short and sweet. Currently this approach does not allow you redirect to a different port number. We have added a new
configuration element that simplifies this setup and allows for cross-port redirects. However since there isn't asadmin support for it yet, I'll defer
discussion until we can get those commands written. That's in the works so it should be in the next week or two.
With that, though, I'll wrap this one up and start working on the more interesting Part 3.
Blog
Newer
Older
Menu
a n t w e r k z
converted by W eb2PDFConvert.com