This indicates that the change did not go into effect. Would gladly appreciate if anyone could shed some light on why some HTTPS websites do not work through the corporate proxy. AH01998: Connection closed to child 3 with abortive shutdown (server :443) ssl_engine_io.c(1227): (70014)End of file found: AH02007: SSL handshake interrupted by system ssl_engine_kernel.c(2008): OpenSSL: Exit: error in unknown state ssl_engine_io.c(2065): OpenSSL: I/O error, 5 bytes expected to read on BIO#562b352aea90 core_filters.c(525): core_output_filter: flushing because of FLUSH bucket ssl_engine_io.c(2056): OpenSSL: write 9/9 bytes to BIO#562b352ba920 (BIO dump follows) ssl_engine_kernel.c(1979): OpenSSL: Loop: unknown state ssl_util_stapling.c(813): AH01956: stapling_cb: setting response ssl_util_stapling.c(697): AH01953: stapling_cb: retrieved cached response ssl_util_stapling.c(314): AH01933: stapling_get_cached_response: cache hit mod_socache_shmcb.c(538): AH00836: leaving socache_shmcb_retrieve successfully mod_socache_shmcb.c(528): AH00835: socache_shmcb_retrieve (0xef -> subcache 3) ssl_util_stapling.c(762): AH01952: stapling_cb: retrieved cached certificate data ssl_util_stapling.c(754): AH01951: stapling_cb: OCSP Stapling callback called protocol.c(1891): select protocol from, choices=h2,spdy/3.1,http/1.1 for server ssl_engine_kernel.c(2096): AH02043: SSL virtual host for servername found ![]() ssl_engine_io.c(2056): OpenSSL: read 11/11 bytes from BIO#562b352aea90 (BIO dump follows) ssl_engine_kernel.c(1979): OpenSSL: Loop: before/accept initialization ssl_engine_kernel.c(1970): OpenSSL: Handshake: start ssl_engine_rand.c(126): Seeding PRNG with 656 bytes of entropy AH01964: Connection to child 3 established (server :443) ![]() I have managed to capture the error logs when a client from the corporate proxy tries to access the website.
0 Comments
Leave a Reply. |