preserveHostHeader ( false ) // Override the Host header sent when reverse proxying to another system (this and the previous parameter are mutually exclusive). enableBrowserProxying ( true ) // Send the Host header in the original request onwards to the system being proxied to. proxyTimeout ( 5000 ) // Make WireMock behave as a forward proxy e.g. ![]() Set the timeout for requests to the proxy in milliseconds. As a proxy, WireMock will trust a target server if it presents a public certificate in this trust store.As a proxy, WireMock will use the private key & certificate in this key store to authenticate its http client with target servers that require client auth. ![]() As a server, when requiring client auth, WireMock will trust the client if it presents a public certificate in this trust store.WireMock uses the trust store for three purposes: trustStorePath ( "/path/to/trust-store.jks" ) // The password to the trust store. needClientAuth ( true ) // Path to the trust store containing the client certificate required in by the previous parameter. keystoreType ( "BKS" ) // Require a client calling WireMock to present a client certificate. keyManagerPassword ( "donttell" ) // Set the keystore type. keystorePassword ( "verysecret!" ) // Set the password to the Jetty's key manager. Previously this set Jetty's key manager password, whereas now it sets the keystore password value. Note: the behaviour of this changed in version 2.27.0. keystorePath ( "/path/to/https-certs-keystore.jks" ) // Set the password to the keystore. Set the keystore containing the HTTPS certificate. WireMock can accept HTTPS connections from clients, require a client to present a certificate for authentication, and pass a client certificate on to another service when proxying. asynchronousResponseThreads ( 10 ) HTTPS configuration # Effective only with asynchronousResponseEnabled=true. asynchronousResponseEnabled ( true ) // Set the number of asynchronous response threads. Recommended when using WireMock for performance testing with delays, as it allows much more efficient use of container threads and therefore higher throughput. jettyHeaderBufferSize ( 16834 ) // Enable asynchronous request processing in Jetty. jettyAcceptQueueSize ( 100 ) // Set the size of Jetty's header buffer (to avoid exceptions when very large request headers are sent). Defaults to Jetty's default of unbounded. jettyAcceptors ( 4 ) // Set the Jetty accept queue size. containerThreads ( 5 ) // Set the number of connection acceptor threads in Jetty. In particular, you will find bidirectional conversions between the following types.// Set the number of request handling threads in Jetty. It is quite easy to do this, because Scala offers implicit conversions between all the major collection types in the JavaConverters object. ![]() Or you might want to pass one of Scala’s collections to a Java method that expects its Java counterpart. ![]() For instance, you might want to access an existing Java collection as if it were a Scala collection. Sometimes you might need to pass from one collection framework to the other. In particular, the Scala libraries put much more emphasis on immutable collections, and provide many more operations that transform a collection into a new one. But there are also important differences. For instance, both libraries know iterators, iterables, sets, maps, and sequences. There are many similarities between the two. Like Scala, Java also has a rich collections library. Info: JavaScript is currently disabled, code tabs will still work,
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |