MockServer is a mock HTTP server that enables easy mocking of any system you integrate with via HTTP or HTTPS (i.e. services, web sites, etc) with clients written in Java, JavaScript and Ruby. MockServer also includes a proxy that introspects all proxied traffic including encrypted SSL traffic and supports Port Forwarding, Web Proxying (i.e. HTTP proxy), HTTPS Tunneling Proxying (using HTTP CONNECT) and SOCKS Proxying (i.e. dynamic port forwarding).
jamesdbloom on maven
jamesdbloom on master
Bump classgraph from 4.8.146 to… (compare)
dependabot[bot] on maven
Bump classgraph from 4.8.146 to… (compare)
jamesdbloom on maven
jamesdbloom on master
Bump json-schema-validator from… (compare)
dependabot[bot] on maven
Bump json-schema-validator from… (compare)
Hi. there. forward is not working.
ClientAndServer clientAndServer = new ClientAndServer(port);
.when(
request()
).forward(
forward()
.withHost("www.google.com")
.withPort(443)
.withScheme(HttpForward.Scheme.HTTPS)
);
and then when I hit at "localhost:2018/", instead of going to google search engine. i am getting 404.
Same thing is happening when trying to forward the request to facebook.com or graph.facebook.com
-Djava.util.logging.config.file=/path/to/example_logging_configuration.properties
param to the docker image? As my understanding this is not possible because of the entrypoint present on the dockerfile on the mockserver.. If I want to override this file, I can't use a docker compose?
version: '3.6'
networks:
default:
name: infinity-network
services:
mockServer:
image: ${MOCKSERVER_IMAGE}
ports:
- 9797:1080
environment:
MOCKSERVER_PROPERTY_FILE: /config/mockserver.properties
volumes:
- ./config:/config
javax.net.ssl|ALL|0E|AsyncHttpClient-3-1|2021-11-12 24:19:18.293 IST|X509Authentication.java:215|No X.509 cert selected for EC
javax.net.ssl|WARNING|0E|AsyncHttpClient-3-1|2021-11-12 24:19:18.293 IST|CertificateRequest.java:764|Unavailable authentication scheme: ecdsa_secp521r1_sha512
javax.net.ssl|ALL|0E|AsyncHttpClient-3-1|2021-11-12 24:19:18.293 IST|X509Authentication.java:215|No X.509 cert selected for RSA
javax.net.ssl|WARNING|0E|AsyncHttpClient-3-1|2021-11-12 24:19:18.294 IST|CertificateRequest.java:764|Unavailable authentication scheme: rsa_pkcs1_sha512
javax.net.ssl|ALL|0E|AsyncHttpClient-3-1|2021-11-12 24:19:18.294 IST|X509Authentication.java:215|No X.509 cert selected for EC
javax.net.ssl|WARNING|0E|AsyncHttpClient-3-1|2021-11-12 24:19:18.294 IST|CertificateRequest.java:764|Unavailable authentication scheme: ecdsa_secp384r1_sha384
javax.net.ssl|ALL|0E|AsyncHttpClient-3-1|2021-11-12 24:19:18.294 IST|X509Authentication.java:215|No X.509 cert selected for RSA
javax.net.ssl|WARNING|0E|AsyncHttpClient-3-1|2021-11-12 24:19:18.294 IST|CertificateRequest.java:764|Unavailable authentication scheme: rsa_pkcs1_sha384
javax.net.ssl|ALL|0E|AsyncHttpClient-3-1|2021-11-12 24:19:18.294 IST|X509Authentication.java:215|No X.509 cert selected for EC
javax.net.ssl|WARNING|0E|AsyncHttpClient-3-1|2021-11-12 24:19:18.294 IST|CertificateRequest.java:764|Unavailable authentication scheme: ecdsa_secp256r1_sha256
javax.net.ssl|ALL|0E|AsyncHttpClient-3-1|2021-11-12 24:19:18.295 IST|X509Authentication.java:215|No X.509 cert selected for RSA
javax.net.ssl|WARNING|0E|AsyncHttpClient-3-1|2021-11-12 24:19:18.295 IST|CertificateRequest.java:764|Unavailable authentication scheme: rsa_pkcs1_sha256
javax.net.ssl|ALL|0E|AsyncHttpClient-3-1|2021-11-12 24:19:18.295 IST|X509Authentication.java:215|No X.509 cert selected for DSA
javax.net.ssl|WARNING|0E|AsyncHttpClient-3-1|2021-11-12 24:19:18.295 IST|CertificateRequest.java:764|Unavailable authentication scheme: dsa_sha256
javax.net.ssl|ALL|0E|AsyncHttpClient-3-1|2021-11-12 24:19:18.295 IST|X509Authentication.java:215|No X.509 cert selected for EC
javax.net.ssl|WARNING|0E|AsyncHttpClient-3-1|2021-11-12 24:19:18.295 IST|CertificateRequest.java:764|Unavailable authentication scheme: ecdsa_sha224
javax.net.ssl|ALL|0E|AsyncHttpClient-3-1|2021-11-12 24:19:18.295 IST|X509Authentication.java:215|No X.509 cert selected for RSA
javax.net.ssl|WARNING|0E|AsyncHttpClient-3-1|2021-11-12 24:19:18.295 IST|CertificateRequest.java:764|Unavailable authentication scheme: rsa_sha224
javax.net.ssl|ALL|0E|AsyncHttpClient-3-1|2021-11-12 24:19:18.295 IST|X509Authentication.java:215|No X.509 cert selected for DSA
javax.net.ssl|WARNING|0E|AsyncHttpClient-3-1|2021-11-12 24:19:18.295 IST|CertificateRequest.java:764|Unavailable authentication scheme: dsa_sha224
javax.net.ssl|ALL|0E|AsyncHttpClient-3-1|2021-11-12 24:19:18.295 IST|X509Authentication.java:215|No X.509 cert selected for EC
javax.net.ssl|WARNING|0E|AsyncHttpClient-3-1|2021-11-12 24:19:18.295 IST|CertificateRequest.java:764|Unavailable authentication scheme: ecdsa_sha1
javax.net.ssl|ALL|0E|AsyncHttpClient-3-1|2021-11-12 24:19:18.296 IST|X509Authentication.java:215|No X.509 cert selected for RSA
javax.net.ssl|WARNING|0E|AsyncHttpClient-3-1|2021-11-12 24:19:18.296 IST|CertificateRequest.java:764|Unavailable authentication scheme: rsa_pkcs1_sha1
javax.net.ssl|ALL|0E|AsyncHttpClient-3-1|2021-11-12 24:19:18.296 IST|X509Authentication.java:215|No X.509 cert selected for DSA
javax.net.ssl|WARNING|0E|AsyncHttpClient-3-1|2021-11-12 24:19:18.296 IST|CertificateRequest.java:764|Unavailable authentication scheme: dsa_sha1
javax.net.ssl|WARNING|0E|AsyncHttpClient-3-1|2021-11-12 24:19:18.296 IST|CertificateRequest.java:774|No available authentication scheme
javax.net.ssl|FINE|0E|AsyncHttpClient-3-1|2021-11-12 24:19:18.297 IST|ServerHelloDone.java:151|Consuming ServerHelloDone handshake message (
<empty>
)
javax.net.ssl|FINE|0E|AsyncHttpClient-3-1|2021-11-12 24:19:18.297 IST|CertificateMessage.java:297|No X.509 certificate for client authentication, use empty Certificate message inste