By craig | March 16, 2020
There are a few settings that can be applied to your ServeUp configuration. Those topics will be covered in this post.
You can also control the port number (default
8080) that ServeUp listens on, and whether it automatically starts listening when ServeUp starts.
Based on the value of this flag, ServeUp will start the web server using a built-in self-signed SSL certificate.
Trusting the SSL Certificate
If your mobile app does certificate-pinning or other SSL validations, you may need to mark this certificate as trusted. The certificate’s FQDN is set to
serveupapp.local so it is much easier if you add the following line to your
Then, in order to make your device or simulator trust the self-signed certificate, start ServeUp with the SSL flag enabled and point your native device’s (or emulator/simulator’s) browser to
https://serveupapp.local:8080/installServeUpSSLCertificate (or whatever port you are using). Follow the prompts to install the certificate as a trusted certificate.
ServeUp can automatically start listening when a particular ServeUp configuration file is opened.
Each response handler has a number of attributes that can control its behaviour. However, there are some settings that can be applied at a global level to override the specific handler settings.
In the example above, all responses would delay for somewhere between 2 and 3 seconds and return a
404 status code.