No response html after authenticated (in Chrome)

[dfeng]

Setting: Chrome, MAMP (localhost:8888)
If I'm not logged in (I'm using the Confide Authentication system, which is just a wrapper for the inbuilt Auth, so that shouldn't be the problem, I don't think), then everything works fine.
Looking at the headers, I get 200 OK, and the response is there.

However, the moment I log in, there is no longer a response. If I navigate to localhost:8888, I get a 200 OK header, but there is no response (no html). Everything sort of loads fine (all the assets), but basically it looks like this:

In Safari and Firefox, however, everything works fine. Baffling...

I don't know how to debug this problem. I've disabled all my extensions in Chrome, to no avail.

I suppose I'm just writing this because I hope it's something stupid I've done (again). Thoughts?

[taylorotwell]

Is there anything in your log files (app/storage/logs)?

[dfeng]

Unfortunately, no.

[vfragosop]

I don't think it has anything to do with framework, but probably a mal formed HTML that is ignored on other browsers. Back in IE6/7 times these were pretty common. Can you try changing your views to something as simples as possible, just to see if it renders? If it does, then there's your answer :)

[dfeng]

That was a great suggestion. I have been able to isolate the problem to the Auth package. It seems that any reference to the Auth package, such as @if (Auth::check()) or {{ Auth::user()->username }}, produces the failed status.

The following route produces the failed status when I'm logged in.

Route::get('test', function(){
  return Auth::user();
});

Nothing in my error logs.

[JoostK]

Can you share the compiled view?

[dfeng]

I'm not sure what you mean by the compiled view. Are you referring to the /storage/views files? (in which case, I'm not sure how to pinpoint which one is the view).

[vfragosop]

Maybe there're some characters being outputted by your model or auth files. Something like this:
http://stackoverflow.com/questions/15211120/laravel-eloquent-outputs-c/

Or maybe the bug envolves cookies somehow, specially since Auth and one specific browser are causing it.

[JoostK]

I mean one of the files in /storage/views, indeed. Unfortunately you have to guess which one it is. Or delete them all, reload your page and the newly compiled view is the view you need 😉

[dfeng]

Okay. I found the problem. It's to do with the Entrust bundle. I will update my comment when I pinpoint the problem. But I'd just like to thank you all for your awesome sleuthing skills!

I couldn't determine the problem - instead, I shall move to Sentry!