error net::ERR_INCOMPLETE_CHUNKED_ENCODING with reverse proxy

[Parker Moore]

Hey everyone,

I have been playing around with camlistore not very seriously for probably the better part of 18 months now and have always found reasons to set it aside. I was inspired by Brad & Mathieu's LinuxFest Northwest talk which I just watched and tried to get camlistore 0.9 setup.

I hit an issue I remember having before: chrome complains of "incomplete chunked encoding."

I am using nginx v1.9.15 with the HTTP2 module turned on as a reverse proxy, passing requests to the `camlistored` running on my server. I thought it was a bug in nginx, but all the other resources load fine.

The only problem I have is loading `/ui/react/react-with-addons.js`. Is this file known to be finicky?

Thanks,

Parker (@parkr)

[Mathieu Lonjaret]

Hi,

Late reply, I had missed that message.
Sorry, I have no idea what that error means, and I have never seen it
before. Have you tried googling for it?

Mathieu

> --
> You received this message because you are subscribed to the Google Groups
> "Camlistore" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to camlistore+...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

[Parker Moore]

Hey Mathieu,

Thanks for the reply.

> Have you tried googling for it?

Yes, and I came up with nada. It's a generic Chrome error.

I upgraded to 0.9 and am now seeing `net::ERR_SPDY_PROTOCOL_ERROR` on the latest Chrome (Version 50.0.2661.86 (64-bit)).

My server is running Nginx 1.9.15 with the HTTP2 module enabled. It reverse proxies to the camlistored service running on the host. It only errors for a handful of JS files:

GET https://camli.example.com/ui/react/react-with-addons.js net::ERR_SPDY_PROTOCOL_ERROR

GET https://camli.example.com/ui/closure/goog/iter/iter.js net::ERR_SPDY_PROTOCOL_ERROR

GET https://camli.example.com/ui/closure/goog/uri/uri.js net::ERR_SPDY_PROTOCOL_ERROR

GET https://camli.example.com/ui/closure/goog/net/xhrio.js net::ERR_SPDY_PROTOCOL_ERROR

GET https://camli.example.com/ui/closure/goog/style/style.js net::ERR_SPDY_PROTOCOL_ERROR

All the CSS loads fine and a number of JS files are fine, too.

On the server, I have the binaries and I ran `go get` on the repo and set the repo root in my GOPATH as the sourceRoot in my server-config.json.

[camlistore@kenny2 camlistore]$ pwd

/home/camlistore/go/src/github.com/camlistore/camlistore

[camlistore@kenny2 camlistore]$ find . -iname react-with-addons.js

./third_party/react/react-with-addons.js

[camlistore@kenny2 camlistore]$ find . -iname iter.js

./third_party/closure/lib/closure/goog/iter/iter.js

[camlistore@kenny2 camlistore]$ find . -iname uri.js

./third_party/closure/lib/closure/goog/uri/uri.js

[camlistore@kenny2 camlistore]$ find . -iname xhrio.js

./third_party/closure/lib/closure/goog/net/xhrio.js

[camlistore@kenny2 camlistore]$ find . -iname style.js

./third_party/closure/lib/closure/goog/style/style.js

./server/camlistored/ui/style.js

How are these resources requested? How are they served via `camlistored`?

Parker

[Mathieu Lonjaret]

Hmm, before we dig any deeper, I'd advise you to retry with the
camlistore source hosted at $GOPATH/src/camlistore.org instead. We
rely enough on this import path that it might just be the cause of
your trouble. If you want to build from source, you should probably
also use 'go run make.go' rather than plain go get, as make.go takes
care of a few other things.

[Parker Moore]

Hm, ok. I fetched that via `go get`, checked out the `0.9` revision and ran `make`.

Now my `serverRoot` is pointed to `$GOPATH/src/camlistore.org`.

I'm now running the binary built by `make` in `$GOPATH/src/camlistore.org/bin/camlistored`.

I stopped my server, started it again, and after a few minutes and a number of refreshes, things started to load.

Thanks! My websocket won't go through, though – getting a 400 for that `wss://` call on every page. Know why that might be? 

Now I just have to rebuild my index...

[Ty Ler]

I'm running reverse proxy and getting 400 on websockets as well

[Ty Ler]

Used nginx config from https://github.com/camlistore/camlistore/issues/816#issuecomment-227925685 and started working

[Mathieu Lonjaret]

just to clarify, do you still have a problem or not?

[Ty Ler]

Problem is resolved. Just like to post resolutions to my problems in case anyone else googles post