These are really good libraries that got my dates and times flowing client-server full circle, with all the UI and math tools I needed.
KISS!
// Date sanitation: limit ancient and future days and ensure start isn't beyond end
date today = second_clock::local_time().date();
date s = startdate;
date e = enddate;
if (e > today)
e = today;
if (e - s > date_duration(cn_max_days_to_look_back))
s = e - date_duration(cn_max_days_to_look_back);
if (s > e)
s = e;
Even the name teaches. Instead of HyperCharts or whatever everyone else is calling themselves, even the name of d3 teaches: let your data drive everything.
One deep dive with haproxy and I have handed it complete control of all my certificates.
* One bind statement with every single cert file I own, and haproxy is instantly handling every host’s SSL handshaking using SNI
* It is handling dynamic conversion of http requests to https
* It has removed the need for https on any webserver on the secured LAN
* It allows incredibly flexible load balancing via host, port, url, etc etc
* It is easy to set up to use ssl best practices, so every one of your websites instantly gets A+ ratings on ssl labs
Unbelievable, I’m stunned.
Here’s all I needed to get ssl labs A+ ratings:
global
# MDM NO SSLv3! Good ciphers!
ssl-default-bind-options no-sslv3 no-tls-tickets force-tlsv12
ssl-default-bind-ciphers AES128+EECDH:AES128+EDH
frontend ....
# MDM We need to provide an HSTS header to get A+ at ssllabs!
http-response set-header Strict-Transport-Security max-age=16000000;\ includeSubDomains;\ preload;
reqadd X-Forwarded-Proto:\ https
Also needed this in wordpress wp-config.php:
if (strpos($_SERVER['HTTP_X_FORWARDED_PROTO'], 'https') !== false)
$_SERVER['HTTPS']='on';
You can directly delete iterators while looping through associative containers like set and map:
for(auto itue = usersByEmail_.begin(), itue_end = usersBySecret_.end(); itue != itue_end; )
{
if ((*itue)->bDeleted())
{
// NOTE We could do more cleanup work here if needed.
itue = usersByEmail_.erase(itue);
} else ++itue;
}
With sequential containers like vector, you should use the erase-remove idiom. Here’s an example for my multi-indexed sets of pointers that uses a lambda to keep the code tight. runsByRank_ is of my sorted_vector type:
runsByRank_.erase(
remove_if(
runsByRank_.begin(), runsByRank_.end(),
[]( StockRun*& psr )
{
// NOTE We could do more cleanup work here if needed.
return psr->bDeleted();
}
),
runsByRank_.end()
);
I’ll try to get my quick-http skeleton app updated with these best practices soon. As of now it does not include any delayed-deletion pattern.
When an unauthenticated user accesses a protected resource of my API server, I want to immediately redirect them to the login page. Research has indicated that the server should send the client an HTTP 302 page with the url. Experimentation has shown that you can successfully set cookies. The cookie can be used to hold the url to re-redirect the user back to the original request after authenticating. Nice.
Here’s the header to send from the server:
const string cstr_HTML_302_HEADER1 = "HTTP/1.1 302 Moved Temporarily\r\nLocation: ";
const string cstr_HTML_HEADER2 = "\r\n\r\n";
// ....
string cookie_header = "\r\n";
cookie_header += "Set-Cookie: .... ";
*response << cstr_HTML_302_HEADER1 << "/v1/login.html" << cookie_header << cstr_HTML_HEADER2;
The publicly available version of quick-http on github needs a refresh, hopefully I'll have some time soon to move a large set of new code there that uses Simple Web Server, HTTP 302 redirects, user authentication, etc.
