[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [MirageOS-devel] TLS deployments/feedback needed
Thinking similarly, I tested whether it crashes serving over cohttp without TLS, and it seems not to; I'll check that next. Also just made an issue: https://github.com/mirage/mirage/issues/406 On 05/20/2015 05:17 PM, Hannes Mehnert wrote: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA384 On 05/20/2015 17:01, Mindy wrote:Good news or bad news, depending on how you slice it: running the extremely naive test script below: ``` for i in `seq 1 2000`; do curl -1 -k https://192.168.3.2/dev/null; done ```against a unikernel generated with mirage-seal results in the following:if instead of invoking the cohttp dispatch (generated by mirage-seal), responding with a static string, does the same issue happen? hannes -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCQAGBQJVXLOCAAoJELyJZYjffCjuNnkP/0W8ztHpLTsU/Z2qoHKQny9d /brhiXNpeDYWh+LsdHQgVpG2heICxcSCr03XHX35o3/7mdEwHhS+r/Y0O6EszFXd ORIIA8824870b1DGMw2Nlx/hm0jA0K1YTOptbRQ+EzeOfPFhduBB7899Uf6IhCyN s9H+4wBOXbhdZjlUSoG/DT0VDkl9VTqgGK1khs1rUtRW8mt70okhe+2PESHsfkeB I/xBS7XtHERxl9UiYNDw8yPAhOAmAjrOlQ8xi8oRm+xEDgbeKF6w8muBul/xL2YU +3LWbryDctTTIBaKqJCG9AMTHSCgKR8q6FAs1QeMSFuzkcotrGHrs28XLa8KxmhF uFTXrAYtcp0imRmLuVEsn41148AMD+Hneio7tBm2LZ+zDyVZxLlsaklrAMBLxmLH V35ceJptWuTASHKuzaAfUtjgj3vw8cFIomNRqFGfspxJHbtYzuB94WnPOWyy4PQv uztu01OiLMaNPfGVpoo0Qy0zsnKQ4UN+lKAaLJ5cDJHKaQyhu4nXor/o79p3KYTm at+bMP3aGekyBBdKXKR7OyZi2dfwYjCUEeSjEnt2rMWrL6FESh793thwWJo6LAaT oGjYktKZE8uRhL7Us/5iKdl5jD4QPdWh48HdfksVKd4JF2zgVL9KE5HPTT9K1Ihq u6EfmDfdtHdwUj1YMqB1 =dD+Y -----END PGP SIGNATURE----- _______________________________________________ MirageOS-devel mailing list MirageOS-devel@xxxxxxxxxxxxxxxxxxxx http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel _______________________________________________ MirageOS-devel mailing list MirageOS-devel@xxxxxxxxxxxxxxxxxxxx http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |