Bug 149957 - [regression] konqueror last svn stop working with xajax library
Summary: [regression] konqueror last svn stop working with xajax library
Status: RESOLVED FIXED
Alias: None
Product: konqueror
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-09-18 08:03 UTC by Martín Lucas Golini
Modified: 2007-10-02 20:24 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martín Lucas Golini 2007-09-18 08:03:35 UTC
Version:            (using KDE Devel)
Installed from:    Compiled sources
OS:                Linux

Im a openSUSE user, the problem happens when update the package of kdebase3 from version   kdebase3-3.5.7-88.3.i586.rpm to kdebase3-3.5.7-88.4.i586.rpm.
Konqueror stop working with xajax library (is an ajax and php library web www.xajaxproject.org), i debug the application with the konqueror debugger and everything seems to be fine, but when i use the internal debugger from xajax i get this error:
"XAJAX DEBUG MESSAGE:
No response processor is available to process the response from the server.<br />Content-Type: undefined"
Its really weird because it was working perfectly before update the version. I can confirm that happens also with the test's and tutorials from the official page.
Thanks for all!
Comment 1 Tommi Tervo 2007-09-18 09:26:13 UTC
I'll add adawit to cc, he committed some fixes to 3.5 branch lately, e.g.
http://lists.kde.org/?l=kde-commits&m=118918730113279&w=2
http://lists.kde.org/?l=kde-commits&m=118870829832535&w=2
Comment 2 Maksim Orlovich 2007-09-18 17:11:08 UTC
http://lists.kde.org/?l=kde-commits&m=118866783529054&w=2 is likely the culprit, it breaks headers completely. (And SUSE should stop shipping snapshots of a branch -- even stable branches can have short-term regressions).

I really need to clean lots of XHR stuff up :(
Comment 3 Ralph Moenchmeyer 2007-09-23 13:13:21 UTC
I have a problem with the handling of http "Refresh" instructions since this Konqueror version. See bug 
http://bugs.kde.org/show_bug.cgi?id=150070 
for more details. 

Bug 150070 could very well be a consequence of some header misinterpretation by the latest Konqueror  versions. 
Please have a look into it and decide whether bug 150070 it is a duplicate of bug 149957.  
Comment 4 Maksim Orlovich 2007-09-28 19:25:44 UTC
*** Bug 150070 has been marked as a duplicate of this bug. ***
Comment 5 Maksim Orlovich 2007-09-28 19:28:33 UTC
From talking to Beineri, these package do likely include the now-reverted r707381; at least the latest 10.3 versions which get rebuilt for 10.2 do. 
So should get fixed once they release proper 3.5.8, or perhaps a later update..
Comment 6 Stephan Binner 2007-10-01 14:51:55 UTC
New kdelibs3 package will be available in KDE:KDE3 later today. And as update for 10.3 later.
Comment 7 Ralph Moenchmeyer 2007-10-02 14:22:30 UTC
Regarding the published rpm's from Oct, 1st (see comment 6):
 
I have just installed the newest versions of kdelibs3 and all other recent KDE:KDE3 updates built for Opensuse 10.2 on Oct., 1st. 
(kdelibs3 version:  kdelibs3-3.5.7-80.1.x86_64.rpm;  kdebase version:  kdebase3-3.5.7-91.2.x86_64.rpm)

Unfortunately, the Konqueror problem I described in bug 150070 is not resolved.  So do the present packages not include the modifications announced by Maksim Orlovich? Do we have to wait for a 3.5.8 version? 

Or is problem 150070 something special that requires other remedies? 
Comment 8 Maksim Orlovich 2007-10-02 17:35:16 UTC
It could perhaps be an another bug related to the http layer work. Could you perhaps check the changelog of the package to see what the latest entries are, though? 
Comment 9 Ralph Moenchmeyer 2007-10-02 18:57:44 UTC
Maxim, below you find the latest changelog entry for kdelibs3-3.5.7-80.1: 
"- SVN commit 717341: Revert r707381 which broke http-headers, and
  add a bit more buffer to handle long http-headers like X-JSON"

Isn't that exactly what you expected?  So, should we reopen bug 150070 again? 
What could I do to analyze my problem in more detail? 
Comment 10 Maksim Orlovich 2007-10-02 20:24:32 UTC
Yes, please reopen 150070. I am not sure of why it would regress though -- don't see any relevant change. Unfortunately that's not something that's easy to test on my end..