Khash Sajadi
Khash Sajadi
Thank you. I can't see the same on the TLS but DNS gets faster which is expected (see below). ``` {"status":200,"error":"","dns_lookup":1835826,"tcp_connection":23338192,"tls_handshake":0,"server_processing":56071368,"content_transfer":618086,"name_lookup":1835826,"connect":25142277,"pre_transfer":0,"start_transfer":81245386,"total":81863472} ❯ curl -H "Content-Type: application/json" http://localhost:8080 --data '{"url":"http://www.google.com","timeout":"1s"}' {"status":200,"error":"","dns_lookup":533888,"tcp_connection":22760430,"tls_handshake":0,"server_processing":58920397,"content_transfer":737248,"name_lookup":533888,"connect":23257384,"pre_transfer":0,"start_transfer":82214715,"total":82951963}...
Here are the responses for `https://www.google.com` and `https://google.com`: ``` ❯ curl -H "Content-Type: application/json" http://localhost:8080 --data '{"url":"https://www.google.com","timeout":"1s"}' {"status":200,"error":"","dns_lookup":17917452,"tcp_connection":17443404,"tls_handshake":163105938,"server_processing":66707585,"content_transfer":1722249,"name_lookup":17917452,"connect":35360856,"pre_transfer":198791702,"start_transfer":265499287,"total":267221536} ❯ curl -H "Content-Type: application/json" http://localhost:8080 --data '{"url":"https://www.google.com","timeout":"1s"}' {"status":200,"error":"","dns_lookup":620721,"tcp_connection":22726986,"tls_handshake":25666911,"server_processing":64927525,"content_transfer":931744,"name_lookup":620721,"connect":23347707,"pre_transfer":49082216,"start_transfer":114009741,"total":114941485} ❯ curl -H...
I understand your point now. I think this behavior depends on what the service is used for. If it is going to be used as a service to provide consistent...
I changed to code to allow system cert to be added at the start (see `features/tls_handshake` branch). However I can't see any difference in timing for the first and consequent...
When trying the code vs the API Playground, the difference is huge as a 0 temperature on the Playground returns the same answer 99% of the time but the code...
This might take a while to implement, but if you can do a PR, more than happy to review and merge
Upon further investigation, the issue is resolved if `default:uuid_generate_v4()` is added to the model: ```go type Foo struct { Id uuid.UUID `gorm:"type:uuid;primary_key;default:uuid_generate_v4()"` Name string } ``` I thought `default:` is...