m</code> is accessed first, it
will return the wildcard certificate (<code>*.test.com</code>) indicating that connections to <code>service2.test.com</code> can use the same certificate.
Browsers like Chrome and Firefox will consequently reuse the existing connection for requests to <code>service2.test.com</code>.
Since the gateway (<code>gw1</code>) has no route for <code>service2.test.com</code>, it will then return a 404 (Not Found) response.</p><p>You can avoid this problem by configuring a single wildca