net::ERR_INCOMPLETE_CHUNKED_ENCODING in Chrome only

Question

I\'ve been getting this error when loading certain pages:

net::ERR_INCOMPLETE_CHUNKED_ENCODING 

These pages don\'t do anything special and

Answer 1

In my case I have "No space left on device". When I delete useless files on Server — error disappeared

Answer 2

This error comes, if you have relationship among domain objects or model object which you are returning back to Jquery. Please annotate with @JsonBackReference, your issue will be resolved

@ManyToOne(fetch = FetchType.LAZY,cascade=CascadeType.ALL)
@JoinColumn(name = "parentId", nullable = false)
@JsonBackReference
public Parent getParent() {
    return this.parent;
}

@OneToMany(cascade=CascadeType.ALLfetch =FetchType.LAZY,mappedBy=      
"parent")
@JsonBackReference
public Set<Category> getChild() {
   return this.child;
}

Answer 3

I've catched the same error on a local website. In logs I found this record:

"nginx failed (13: Permission denied) while reading upstream, client:   127.0.0.1".

My decision through restart of nginx and php-fpm from the right user:

Let's my_user – main user of website's directory.

First, go to nginx.conf: Change

user nginx; -> user my_user my_user_group;

or paste this

user my_user my_user_group;

on the top of file

2) Second, in php5/fpm/pool.d/www.conf

# Find and change this variables from old -> to new:
user -> my_user
group -> my_user
listen.owner -> my_user
listen.group -> my_user

3) And finally you need restart of nginx and php-fpm. Then make chown 0700 in handmode for /var/lib/nginx/tmp for my_user, like this:

chown -R my_user:my_user 0700 /var/lib/nginx/tmp

Answer 4

We had net::ERR_INCOMPLETE_CHUNKED_ENCODING problem in case of HTML, which contained too much empty lines. Some browsers had difficulties with interpretation of long files.

Once we've made code cleaning in our templates by cleaning the code from empty lines, error disappeared.

Answer 5

I have met this problem yesterday. It's because of the server didn't response some resources.

In my page, i have some large file links like<a href="/file_path">file_name</a>, and this happend only in chrome.

In a while ,I recognized this maybe caused by the chrome's 'Predict network actions to improve page load performance' feature.So I turned off this feature in chrome://settings and try it again. As expected, the error didn't occur again.

After that, I changed resource links with full_url_path instead of relative_path(in rails, use resource_url instead of resource_path), then I didn't have to turn off the chrome's feature. And it looks good.

Answer 6

I had this in a symfony project (PHP).

Like you describe your issue I had some static page (html.twig) with simple HTML and CSS... so nothing special about it.

For me it was a mod_rewrite problem, after I enabled mod_rewrite and added FallbackResource /index.php to my vhost it all worked smoothly.

PS: if you have apache lower than 2.2.16 create a .htaccess file in your root folder and use this code:

Options -MultiViews

RewriteEngine On
#RewriteBase /path/to/app
RewriteCond %{REQUEST_FILENAME} !-f
RewriteRule ^ index.php [QSA,L] </IfModule>