edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev]  [PATCH] Implement the "novs" directive.
Date: Fri, 12 Sep 2014 17:10:32 -0400	[thread overview]
Message-ID: <20140812171032.eklhad@comcast.net> (raw)

This looks good.
You could submit it and I would be fine with that.

I do have a couple small questions though.
The first is just style / consistency.
You use strcasecmp for I guess string compare case insensitive.
A library function I didn't know about?
I use throughout stringEqualCI, which I wrote myself.
Should we always use one, or the other?
Mine is part of a suite of such CI functions, like mem compare CI and so on,
I'm sure not all have library equivalents.

You took the time to add sites in a growing dynamic list,
which is right, sometimes I was too lazy to do that.
Like nojs, I store 100 sites for no javascript and that's it.
Any time you, or I, feel like making this dynamic, feel free.
Same for email accounts, though I can't imagine anyone having
more than 100 of those.
And maybe other static lists floating around.

When you check for novs match you need an exact match.
Not so for nojs.
whatever.com will also have no javascript for subdomains
like foo.whatever.com.
See the code in main.c that does that.
Should we do the same for novs?
I would think so; if there's no cert for whatever.com
then there is for sure no cert for foo.whatever.com.


Karl Dahlke

             reply	other threads:[~2014-09-12 21:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-12 21:10 Karl Dahlke [this message]
2014-09-12 21:34 ` Chris Brannon
2014-09-16 20:41   ` Adam Thompson
2014-09-16 20:58     ` Chris Brannon
  -- strict thread matches above, loose matches on Subject: below --
2014-09-11 19:06 Christopher Brannon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140812171032.eklhad@comcast.net \
    --to=eklhad@comcast.net \
    --cc=Edbrowse-dev@lists.the-brannons.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).