| Summary: | UPNP plugin don't get xml | ||
|---|---|---|---|
| Product: | [Applications] ktorrent | Reporter: | BLaD <blad_temp> |
| Component: | general | Assignee: | Joris Guisson <joris.guisson> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | blad_temp, diegocg, vovochka13 |
| Priority: | NOR | ||
| Version First Reported In: | 4.3.1 | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: |
Ktorrent logs file
ktupnptest log file Wireshark's dump of ktupnptest Wireshark's dump of ktorrent UPNP |
||
|
Description
BLaD
2014-03-05 18:07:27 UTC
Created attachment 85429 [details]
Ktorrent logs file
Created attachment 85430 [details]
ktupnptest log file
Created attachment 85431 [details]
Wireshark's dump of ktupnptest
Created attachment 85432 [details]
Wireshark's dump of ktorrent UPNP
I can confirm something like this is happening in my system. UPnP plugin doesn't work, and I see this in the log: jue may 29 14:13:10 2014: Detected IGD ipos/7.0 UPnP/1.0 TL-WR740N/4.0 jue may 29 14:13:10 2014: Downloading XML file http://192.168.0.1:1900/igd.xml jue may 29 14:13:10 2014: Error parsing XML I can access http://192.168.0.1:1900/igd.xml with firefox But, surprisingly, it does not work at all with konqueror - it shows "500 Internal Server Error" This makes me think that the bug is not in ktorrent, but somewhere in the http KDE stack. Well, I just found and fixed the problem. Apparently, the bug is NOT in KDE. It is in the router - both the original reporter and me have a TP-LINK router. Apparently, the web server included in TP-LINK router is broken. It returns error when the browser user agent is unknown to it. To fix the problem , you've got to go to the konqueror preferences -> browser identification Then go to "Site specific identification"->"new", and add a site identification for your router's IP (192.168.1.1 in case of the bug reporter), then select a modern Windows IE browser in the agent list. Then restart konqueror (for some reason it requires it in order to work). Then restart ktorrent - problem solved! You might be right, although the solution is quite dubious and not transparent. As I said ktupnptest works fine with my router. I do not think that there is a problem to do the same user agent. And ofc thank you. The latest release of ktorrent (5.1.0) has solved this issue for me Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you! Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |