Version: (using KDE KDE 3.5.4) Installed from: Unlisted Binary Package I'm developing small Dojo app. I'm hosting&testing it on my localhost apache server. When I open my app in firefox - it works. When I open it under konq. it does not. Dojo error message says that dojo can't load one of the modules (always the first one it has to). After analyzing apache access logs I discovered that when HTTP 304 return code is returned by server on *.js file GET request, konq&dojo behave like it was 404 - just tries to GET other standard paths for this module insted of using cache content. So I turned of http cache in konq. No cache => no conditional GET => no 304 => my app works in konq. I turn cache on, app stops working. I have only used dojo so far - I'm not sure if this isn't dojo's problem and I lack time (and knowledge) to judge anything, but I wish to report that anyway. I can provide any additional info if required.
Is it still the case in KDE 4.0 beta? Do you have any test-cases? Somewhere it can be tested.
Hmm, I actually have a patch I forgot to commit for #146384, where we don't change 304->200 for synchronous path. The thing is, the current substitution is wrong, as it can actually change other headers, not just the result code.
Hi! What about this bug? Is still valid with KDE 4?
Closing for lack of feedback.