[Webkit-unassigned] [Bug 62852] cannot handle status codes which have no response body

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=62852





--- Comment #11 from Keunsoon Lee <keunsoon.lee at samsung.com>  2011-07-26 23:00:19 PST ---
(In reply to comment #10)
> What kind of information are you looking for that is not currently available?
> 
> For instance, a FrameLoaderClient gets a pointer to document loader in dispatchDidLoadMainResource(). It also gets it in committedLoad(), together with the data that triggered the commit. Also, from virtually any callback it can access its frame's active document loader, and any information associated with it.
> 
> The problem I see with implementing the behavior you described is one of choice - there are so many ways to do it that it's hard to pick one that works best in edge cases. Adding one more similar callback will only make the problem worse.

I thought giving an exact notice for the situation via separate function would be the best way.
But, now I agree with you that adding a similar function can make client confused rather than help.

Furthermore, Adam Barth said (on chat) that different behavior for specific status code on FrameLoader would not be a good choice.

Now, I'm studying Chromium port to solve this situation because I heard it can solve this problem without any touch on FrameLoader.


Thank you for your comment!

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.