ERR_INCOMPLETE_CHUNKED_ENCODING Chrome Root page load

前端 未结 4 1107
遇见更好的自我
遇见更好的自我 2021-01-11 09:51

I have a website on a lamp stack with little to no extra configuration other than FallbackResource /index.php present in my root .htaccess

When I load t

相关标签:
4条回答
  • 2021-01-11 10:14

    In my json response '\n' causing the issue. So after removing it, issue has been solved.

    0 讨论(0)
  • 2021-01-11 10:21

    Finally found the answer while working on another site:

    Before FallbackResource directive be sure to add a DirectoryIndex directive with the same file. Haven't had time to research why but it fixed my issue. I blame it on a Chrome bug or possibly Chrome being super picky because no other major browser has an issue.

    0 讨论(0)
  • 2021-01-11 10:25

    To add to Blaine's answer (as I can't yet comment):

    I believe this is an Apache configuration issue, not specific to Chrome.

    I recently experienced this issue, and noted the following effects in various clients, again only with the home page:

    • Chrome, as stated, displayed the ERR_INCOMPLETE_CHUNKED_ENCODING error, but also didn't display the page correctly. The page continued to "load" for another 5 seconds even after all the content was visible.
    • A simple CURL request outputted the error curl: (18) transfer closed with outstanding read data remaining. The full HTML appeared, followed by the error after a delay.
    • Firefox and IE initially displayed the page incorrectly, as with Chrome, and again had the ~5 second additional loading time. However, after this period, the page suddenly reformatted itself correctly. No errors were seen in the respective developer consoles.

    The solution to set the DirectoryIndex to the same location as FallbackResource resolved this for all clients.

    Edit: An alternative if using mod_rewrite is to use something like RewriteRule ^$ index.php which will avoid affecting all subdirectories.

    I don't know whether this is expected behaviour of Apache or a bug.

    0 讨论(0)
  • 2021-01-11 10:27

    I fixed this error by removing the following lines from my php5filter.conf file in the Apache configuration:

    <FilesMatch ".+\.ph(p3?|tml)$">
        SetInputFilter PHP
        SetOutputFilter PHP
    </FilesMatch>
    
    0 讨论(0)
提交回复
热议问题