版本
v4.1.0 windows x64

启动命令 :
.\pike.exe --admin=:9013

访问 127.0.0.1:9013 出现错误：

{"statusCode":500,"category":"elton-error","message":"open web\index.html: file does not exist","exception":true}

支持https吗?是否以后会增加呢?

根据HTTP请求头中的：Accept-Encoding:gzip, deflate, br，对于支持brotli压缩的客户端，使用br压缩返回。

Background

The go-yaml/yaml has already renamed it’s import path from "github.com/go-yaml/yaml" to "gopkg.in/yaml.v2".
As README of go-yaml/yaml v2.1.0 said, downstream repos should use "gopkg.in/yaml.v2" to get or import go-yaml/yaml.

Example
Some more examples can be found in the "examples" folder.

package main
import (
        "fmt"
        "log"
        "gopkg.in/yaml.v2"
)
…

But vicanso/pike still used the old path:
https://github.com/vicanso/pike/blob/master/go.mod#L10

github.com/go-yaml/yaml v2.1.0+incompatible 

When you use the old path "github.com/go-yaml/yaml" to import the go-yaml/yaml, it will be very easy to reintroduce go-yaml/yaml through the import statements "import gopkg.in/yaml.v2" in the go source file of go-yaml/yaml.
https://github.com/go-yaml/yaml/blob/v2.1.0/decode_test.go#L12

package yaml_test
import (
	…
	. "gopkg.in/check.v1"
	"gopkg.in/yaml.v2"
)

The "gopkg.in/yaml.v2" and "github.com/go-yaml/yaml" are the same repos. This will work in isolation, bring about potential risks and problems.

Solution

Replace all the old import paths, change "github.com/go-yaml/yaml" to "gopkg.in/yaml.v2".
Where did you import it: https://github.com/vicanso/pike/search?q=github.com%2Fgo-yaml%2Fyaml&unscoped_q=github.com%2Fgo-yaml%2Fyaml

根据响应的Content-Type以及客户端的请求头Accept:text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,image/apng,/;q=0.8，选择更优的webp图片格式

日志中返回400，日志中能否看出是否被命中，从日志中看好像全部打到源服务器去请求了

如果接口返回为No Content(204)时，报 EOF 出错

但是我看了一下.. decoe.h 文件是存在的。。

First of all want to admire your project. Its the best and most complex opensource cashing software out there. Keep the good work!

Second i like to propose several new new feature requests and if possible to discus them (from what i see form the code you have impressive knowledge about http protocol specially in the optimization aspect)

First proposal is about several instances that use a distributed cache:
Ref : https://github.com/golang/groupcache

Second is related to abstraction of the upstreams.
To be able to handle GCS or S3 buckets as upstream

Third one is for UI : options to display some statistics like miss/hit ratio and ability to purge cache entries.

And documentation is a bit foggy Took me about a 3 days to run the app with my scenario but at the end results are impressive !

{remote} {when-iso} {:proxyTarget} {method} {uri} {proto} {status} {size-human} {referer} {userAgent}
从那里面能看到日志，好像没有产生新文件

1、如何配置某个url缓存多长时间
2、能否根据参数配置缓存的key，比如参数是 a=1&b=2&c=3&d=4 其中c和d参数都无用，只想根据a b参数缓存
3、能否根据resp header判断是否缓存，缓存多长时间（varnish支持）

docker run -d --restart=always -p 3015:3015 -v ./config.yml:/etc/pike/config.yml vicanso/pike
不知道是不是我服务器的问题。。 docker映射目录一定要绝对路径吧。。