40kb limit on html files about grunt-contrib-connect

[daspecster]

Can anyone verify that this is an issue? Confirm/Deny?

[sindresorhus]

Confirmed. Looks like it was a bug in the connect version we were using. Upgraded connect and seemed to work fine.

Try out 0.2.0 ;)

[daspecster]

Still seems to be broken :( We have a video coming soon to demonstrate...when vimeo gets doen processing it'll be here... https://vimeo.com/61268804

Video curtesy of @stephenplusplus

[sindresorhus]

Sorry, forgot to npm publish :/

It's up now.

[stephenplusplus]

Hey @sindresorhus, I actually tested with 0.2.0 by manually cloning it into daspecsters-example-project/node_modules. npm installed, which got [email protected], and then grunt server'd the project. Still clipped the .html at 40k.

Same result by updating the project's /package.json with 0.2.0 for grunt-contrib-connect.

[sindresorhus]

Alright, so I've narrowed it down to the livereloadSnippet, no idea why it worked for me though, might be some unclosed connection or something. Anyway, seems like the html is cut of because the content-length is never set to more than 40kb (that being the max buffer size).

https://github.com/gruntjs/grunt-contrib-livereload/blob/master/lib/utils.js

Can you open an issue on grunt-contrib-livereload?

[daspecster]

Brilliant! I will do that right now!

https://github.com/gruntjs/grunt-contrib-livereload/issues/25

Thanks for all your help too btw!

[jgallen23]

I'm still having this issue with the latest grunt-contrib-connect and using livereload: true. Anybody else?

[tschlich]

same problem here... does not work with grunt-contrib-connect 0.2.0 and 0.5.0

[shama]

Would you guys mind opening the issue on https://github.com/intesso/connect-livereload? That is the underlying library that handles this part of the task now. Thanks!

[jgallen23]

one thing I just noticed is that when I npm install grunt-contrib-connect, I get connect-livereload 0.2.0, but in the git repo, I see connect-livereload: 0.3.0.

[jgallen23]

confirmed that when connect-livereload 0.3.0 is used the issue goes away. So I think the fix is to publish a new version of grunt-contrib-connect to npm with connect-livereload ~0.3.0 as a dependency.

Just an FYI, if you run npm info grunt-contrib-connect it shows:

dependencies:
   { connect: '~2.7.11',
     'connect-livereload': '~0.2.0',
     open: '0.0.4' },

[andineck]

if you push a new version, please use the latest one of connect-livereload: 0.3.1

[shama]

Ah strange. Ok reopening to remind me to do this. Thanks!

[shama]

Fixed on 0.6.0.

[razvan-flavius-panda]

Still getting this bug on the latest grunt-contrib-connect @0.7.1 (it depends on 'connect-livereload': '~0.3.0')

The use case is a html view file being served by AngularJS using XHR. The file served is around 100 KBytes and gets truncated at the end.

[kevin-smets]

This is still an issue for us, has this been looked into further?

[haxaco]

Same here, our pages are being cut and we're working with grunt contrib watch (0.6.1) and connect (0.9.0). Should we roll back to 0.6.0?

[andineck]

It once was an issue with connect-livereload, but it should have been fixed... I quickly checked the versions: grunt-contrib-connect 0.9.0 uses connect-livereload 0.5.0 (the latest one would be 0.5.0), but this bug was supposed to be fixed in 0.5.0 already.
intesso/connect-livereload@v0.5.0...v0.5.2

there is a test with large files (~2.9MB):
https://github.com/intesso/connect-livereload/blob/master/test/app.render.large-file.js

anyway, can you send me a test file or add a test case to connect-livereload?

[andineck]

I just updated connect-livereload's test dependencies and added another test case with connect and large files. v0.5.3.

The tests run with:
"connect": "^3.3.4",
"express": "~4.11.2",

[andineck]

do you use some other middleware with size limits? e.g.:
https://github.com/expressjs/body-parser#limit