diff --git a/blog/2013-07-09-Undertow-Beta1-Released.asciidoc b/blog/2013-07-09-Undertow-Beta1-Released.asciidoc index 9bb9960c..7fac4557 100644 --- a/blog/2013-07-09-Undertow-Beta1-Released.asciidoc +++ b/blog/2013-07-09-Undertow-Beta1-Released.asciidoc @@ -10,7 +10,7 @@ Stuart Douglas :Date: 2013-07-09 :Revision: 1.0 -Undertow is a high performance non-blocking webserver that is the new web server in Wildfly. +Undertow is a high performance non-blocking webserver that is the new web server in WildFly. Some notable features include: diff --git a/blog/2015-03-26-HTTP2-In-Wildfly.asciidoc b/blog/2015-03-26-HTTP2-In-Wildfly.asciidoc index f18f3ff4..2798ba15 100644 --- a/blog/2015-03-26-HTTP2-In-Wildfly.asciidoc +++ b/blog/2015-03-26-HTTP2-In-Wildfly.asciidoc @@ -2,7 +2,7 @@ layout: project-blog --- -Using HTTP2 With Wildfly 9.0.0.Beta1 +Using HTTP2 With WildFly 9.0.0.Beta1 ==================================== Stuart Douglas :Author: Stuart Douglas @@ -11,7 +11,7 @@ Stuart Douglas :Revision: 1.0 -The upcoming Wildfly 9.0.0.Beta1 release supports HTTP2, which includes new features like request multiplexing and +The upcoming WildFly 9.0.0.Beta1 release supports HTTP2, which includes new features like request multiplexing and server push, unfortunately due to a few different factors it is not as straightforward to set up as HTTP1. The complexity comes because HTTP2 as implemented by major browsers requires the use of TLS. This is further complicated by the fact that it does not use straight TLS, but requires a extension called ALPN (application layer protocol negotiation). @@ -30,14 +30,14 @@ The TL;DR version ------------------ Make sure you are using *JDK 1.8.0u40*, then run the script below. This will (hopefully) perform all the steps that are -required to setup Wildfly. +required to setup WildFly. [source,bash] ---- #!/bin/bash if [ "x$JBOSS_HOME" == "x" ]; then - echo "JBOSS_HOME is not set, please set it to the root of your Wildfly installation" + echo "JBOSS_HOME is not set, please set it to the root of your WildFly installation" exit fi @@ -60,9 +60,9 @@ curl http://central.maven.org/maven2/org/mortbay/jetty/alpn/alpn-boot/$ALPN_VERS #Add ALPN to the boot class path echo 'JAVA_OPTS="$JAVA_OPTS' " -Xbootclasspath/p:$JBOSS_HOME/bin/alpn-boot-$ALPN_VERSION.jar" '"' >>bin/standalone.conf -#Start Wildfly in the background +#Start WildFly in the background ./bin/standalone.sh & -#wait for Wildfly to start +#Wait for WildFly to start sleep 15 #Add a HTTPS connector @@ -71,7 +71,7 @@ sleep 15 ./bin/jboss-cli.sh -c "--command=/core-service=management/security-realm=https/server-identity=ssl:add(keystore-path=server.keystore, keystore-password=password, keystore-relative-to=jboss.server.config.dir)" ./bin/jboss-cli.sh -c "--command=/subsystem=undertow/server=default-server/https-listener=https:add(socket-binding=https, security-realm=https, enable-http2=true)" -#shut down Wildfly +#Shut down WildFly kill `jps | grep jboss-modules.jar | cut -f1 -d ' ' ` ---- @@ -81,7 +81,7 @@ A step by step guide Figure out the correct Jetty ALPN Jar for your JDK version:: Have a look at http://eclipse.org/jetty/documentation/current/alpn-chapter.html to figure out which version of Jetty ALPN is required for your JVM version. Download the correct jar version from -link:http://central.maven.org/maven2/org/mortbay/jetty/alpn/alpn-boot/[maven central] and place it in the Wildfly bin +link:http://central.maven.org/maven2/org/mortbay/jetty/alpn/alpn-boot/[maven central] and place it in the WildFly bin directory. Add ALPN to the boot class path:: @@ -93,10 +93,10 @@ For testing purposes you can download the ones from the Undertow test suite that production use you will need to create a certificate and get it signed by a certificate authority. For the purposes of these instructions we assume they are located in standalone/configuration/server.[keystore|truststore]. -Start Wildfly:: -We are going to make the remaining changes using the CLI, which means Wildfly must be started. +Start WildFly:: +We are going to make the remaining changes using the CLI, which means WildFly must be started. -Connect to Wildfly using the CLI:: +Connect to WildFly using the CLI:: Run the following command to connect: `$JBOSS_HOME/bin/jboss-cli.sh -c`. Add a security realm:: @@ -119,7 +119,7 @@ Add a HTTPS connector:: Test it out:: Fire up Chrome and head to link:https://localhost:8443[https://localhost:8443]. After clicking through the security warning -about the self signed certificate you should see the normal Wildfly welcome page. Open up the developer tools and have +about the self signed certificate you should see the normal WildFly welcome page. Open up the developer tools and have a look in the 'Network' tab. In the request headers section you should see chrome sending HTTP2 pseudo headers (:path, :authority, :method and :scheme). You can also look in the `chrome://net-internals` page, and you should be able to see the details of the HTTP2 session (although it will show up as a SPDY_SESSION event, as diff --git a/blog/2019-04-15-Undertow-3.0-announcement.asciidoc b/blog/2019-04-15-Undertow-3.0-announcement.asciidoc index 7bb0c18b..ed740989 100644 --- a/blog/2019-04-15-Undertow-3.0-announcement.asciidoc +++ b/blog/2019-04-15-Undertow-3.0-announcement.asciidoc @@ -19,7 +19,7 @@ The underlying transport implementation are the most complex part of Undertow, d As part of this Flavia Rainone will be taking over as project lead from Stuart Douglas so he can focus on the recently announced Quarkus project, however Stuart will continue to be heavily involved in Undertow for the foreseeable future. -Flavia Rainone has been involved in JBoss community since 2002 and has an extensive background on Remoting and Xnio. In the past years, she acted as EJB component lead for Wildfly, besides contributing to several projects in Wildfly, such as IronJacamar, JBoss MSC and XNIO, and also Byteman. All this makes her a good fit for taking over Undertow leadership. +Flavia Rainone has been involved in JBoss community since 2002 and has an extensive background on Remoting and Xnio. In the past years, she acted as EJB component lead for WildFly, besides contributing to several projects in WildFly, such as IronJacamar, JBoss MSC and XNIO, and also Byteman. All this makes her a good fit for taking over Undertow leadership. === What does this mean for me? @@ -55,4 +55,4 @@ Jira issues can be accessed here: https://issues.jboss.org/projects/UNDERTOW/iss And source code for 3.x is here: https://github.com/undertow-io/undertow/tree/3.x -Also, with the move from HipChat to Zulip in Wildfly team, you can now access Undertow stream via Zulip at https://wildfly.zulipchat.com/ \ No newline at end of file +Also, with the move from HipChat to Zulip in WildFly team, you can now access Undertow stream via Zulip at https://wildfly.zulipchat.com/ \ No newline at end of file diff --git a/downloads.asciidoc b/downloads.asciidoc index 94648fa8..e9d84aff 100644 --- a/downloads.asciidoc +++ b/downloads.asciidoc @@ -14,9 +14,9 @@ Downloads --------- The easiest way to get started using Undertow is to download the -link:http://www.wildfly.org/downloads/[Wildfly Application Server]. +link:http://www.wildfly.org/downloads/[WildFly Application Server]. -Undertow is the default web server in Wildfly, so usage is as simple as deploying a war. +Undertow is the default web server in WildFly, so usage is as simple as deploying a war. Maven ~~~~~ diff --git a/index.asciidoc b/index.asciidoc index d3404551..de976163 100644 --- a/index.asciidoc +++ b/index.asciidoc @@ -22,7 +22,7 @@ handler, to anything in between. Undertow is designed to be fully embeddable, with easy to use fluent builder APIs. Undertow's lifecycle is completely controlled by the embedding application. -Undertow is sponsored by JBoss and is the default web server in the link:https://github.com/wildfly/wildfly[Wildfly Application Server]. +Undertow is sponsored by JBoss and is the default web server in the link:https://github.com/wildfly/wildfly[WildFly Application Server]. Why Undertow ------------ diff --git a/wildfly-http2.sh b/wildfly-http2.sh index d2e0cf75..15bd7930 100755 --- a/wildfly-http2.sh +++ b/wildfly-http2.sh @@ -1,7 +1,7 @@ #!/bin/bash if [ "x$JBOSS_HOME" == "x" ]; then - echo "JBOSS_HOME is not set, please set it to the root of your Wildfly installation" + echo "JBOSS_HOME is not set, please set it to the root of your WildFly installation" exit fi @@ -24,9 +24,9 @@ curl http://central.maven.org/maven2/org/mortbay/jetty/alpn/alpn-boot/$ALPN_VERS #Add ALPN to the boot class path echo 'JAVA_OPTS="$JAVA_OPTS' " -Xbootclasspath/p:$JBOSS_HOME/bin/alpn-boot-$ALPN_VERSION.jar" '"' >>bin/standalone.conf -#Start Wildfly in the background +#Start WildFly in the background ./bin/standalone.sh & -#wait for Wildfly to start +#Wait for WildFly to start sleep 15 #Add a HTTPS connector @@ -35,5 +35,5 @@ sleep 15 ./bin/jboss-cli.sh -c "--command=/core-service=management/security-realm=https/server-identity=ssl:add(keystore-path=server.keystore, keystore-password=password, keystore-relative-to=jboss.server.config.dir)" ./bin/jboss-cli.sh -c "--command=/subsystem=undertow/server=default-server/https-listener=https:add(socket-binding=https, security-realm=https, enable-http2=true)" -#shut down Wildfly +#Shut down WildFly kill `jps | grep jboss-modules.jar | cut -f1 -d ' ' ` \ No newline at end of file