Using TLS and HTTP/2 in development Permalink to " Using TLS and HTTP/2 in development"
Introduction Permalink to "Introduction"
This page is for using TLS and HTTP/2 in development (mainly for testing purposes). For production configuration, please read the security section in the production documentation.
TLS is the protocol used when having an
https:// URL, and it is required in order to use HTTP/2 on modern browsers.
It is useful to use those protocols when testing an application, mainly for performance reasons.
Using TLS and HTTP/2 with Spring Boot Permalink to "Using TLS and HTTP/2 with Spring Boot"
JHipster has a specific configuration for configuring both TLS and HTTP/2 (see the common application properties documentation), and in order to make things even simpler:
- JHipster generates a self-signed certificate at application generation
- A specific
tlsprofile is provided (see the profiles documentation)
In order to run JHipster with the provided self-signed certificate, with TLS and HTTP/2 enabled, you need to use the
- with Maven:
- with Gradle:
The application will be available on
As the certificate is self-signed, your browser will issue a warning, and you will need to ignore it (or import it) in order to access the application.
Using TLS and HTTP/2 with Angular or React or Vue.js Permalink to "Using TLS and HTTP/2 with Angular or React or Vue.js"
Instead of using
npm start in order to run the front-end (with Webpack and BrowserSync), run
npm run start-tls, and it will connect to the back-end running on
Everything should then work the same as without TLS and HTTP/2.