Does buildsrv cache plugin versions for a long time?


I have fixed Sometimes an invalid content length error is produced · Issue #3 · echocat/caddy-filter · GitHub 22 days ago. But when I go to Download Caddy and try to download the latest caddy version with the filter plugin this bug could still be reproduced. If I build (in a clean GOPATH) on my local disk and only add the following line to

    _ ""

…everything works perfektly. :confused:

Hint: There are no special branches in - only master.

Any ideas?

/ Gregor

Here is a way to reproduce that the bare metal way works:

1. Start and enter a new and clean docker container

docker run --rm -ti -p 2020:2020 golang

2. Prepare and start Caddy with caddy-filter

# Download caddy sources with all dependencies
go get -u
# Download caddy-filter with all dependencies
go get -u

# Configure caddy to use caddy-filter
sed -i 's/\t\/\/ This is where other plugins get plugged in (imported)/\t_ "\/echocat\/caddy-filter"/' $GOPATH/src/

# Add Caddyfile
cat << EOF > /tmp/Caddyfile
root /tmp
filter rule {
  content_type text/.*
  search_pattern "Replace me!"
  replacement "OK!"

# Add example index file
cat << EOF > /tmp/
<head><title>Replace me!</title></head>
<body><p>Replace me!</p></body>

# Build caddy
go build -o $GOPATH/bin/caddy

# Run caddy
caddy -conf /tmp/Caddyfile

#3. Check result
Open http://localhost:2020 and you should see the text OK! in your browser. If you see Replace me! or an error the latest fixes was not applied to this build.

The build server caches them indefinitely, until I update it. I have to update the build server manually until the new website is released. Sorry :confused: I’ll try to get to it sometime.

No worries! :slight_smile:

I hope we can flush this in the near future because I fixed to important issues for some guys and I’am happy to broad it to them as fast as possible. Thank you for your time. :tropical_drink:

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.