Coming from qs we would control how arrays in query parameters would be with the arrayFormat option (quote from qs docs below):

You may use the arrayFormat option to specify the format of the output array:

qs.stringify({ a: ['b', 'c'] }, { arrayFormat: 'indices' })
// 'a[0]=b&a[1]=c'
qs.stringify({ a: ['b', 'c'] }, { arrayFormat: 'brackets' })
// 'a[]=b&a[

It would be nice to enable a generic fn that can be used to hack add customize use cases

function filterFunc(key, value) {
   if (key == 'b') {
       // Return an `undefined` value to omit a property.
       return;
   }
   if (key == 'e[f]') {
       return value.getTime();
   }
   if (key == 'e[g][0]') {
       return value * 2;
   }
   return value;
}

1. The example configuration of tunnel.yml: indent charaters uses both tab and spaces, which makes it not parsable.
   2 After fixed 1, client throws the following error:

configuration error: tls invalid protocol "sni"

Client version: 2.1

If I create a furl object without a scheme like so:

>>>from furl import furl
>>>x = furl('www.google.com')

It fails in weird ways that aren't exactly intuitive.

I would expect that furl should either raise an error here or create a URL without a scheme.

Instead I get weird results like:

>>> g.origin
'://'
>>> g.host
>>> g.netloc

Ideas:

• Set a minimum dimension for images.
• Find a way to detect dimensions before downloading the image.

Currently most of the examples in the README expect something after the /. Given that matching the "empty path" is a very common scenario users will want to accomplish it could be documented more prominently. I don't have more than anecdotal data on this but I'd expect that it is also often a source of confusion.

(def my-routes ["/" {"" :index ; I'm not even sure if this is correc

As an occasional standards-user, the lack of a succinct expression of the grammar for valid URL strings is rather frustrating. It makes it rather difficult to follow what's going on and, in particular, to work out whether a given thing is a valid URL. A grammar in EBNF or a similar form would be greatly appreciated and make this spec significantly easier to understand.

bannedregexpurllist:

котик
kitty

e2guardian.conf:

weightedphrasemode = 1
phrasefiltermode = 2
preservecase = 2
hexdecodecontent = off
forcequicksearch = on

When I visit, for example, http://blank.org/?котик - request is blocked, all ok. But when I visit http://blank.org/?КОТИК or http://blank.org/?Котик - all passes.
When I enter http://blank.org/?kitty or http://bl

Input:

new URL('http://a.com')

Output:

{
  ...
  href: 'http://a.com/',
  origin: 'http://a.com:80',
  port: '80',
  ...
}

Expected (as is in Chrome):

{
  ...
  href: 'http://a.com/',
  origin: 'http://a.com',
  port: '',
  ...
}

Edit: this consequence seems to occur in IE only :/