Bug 12328 - www.ddnss.de provider unhandled exception
Summary: www.ddnss.de provider unhandled exception
Status: CLOSED FIXED
Alias: None
Product: DDNS Updater
Classification: Unclassified
Component: Providers (show other bugs)
Version: unspecified
Hardware: x86_64 Unspecified
: - Unknown - Minor Usability
Assignee: Stefan Schantl
QA Contact: Michael Tremer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-03-20 10:07 UTC by Carsten Harms
Modified: 2020-12-29 17:08 UTC (History)
4 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Carsten Harms 2020-03-20 10:07:34 UTC 
Dynamic DNS update for ***.ddnss.de (DDNSS) threw an unhandled exception: Trac eback (most recent call last): File "/usr/lib/python3.8/site-packages/ddns/__i nit__.py", line 164, in _update entry(force=force) File "/usr/lib/python3. 8/site-packages/ddns/providers.py", line 158, in __call__ self.update() Fi le "/usr/lib/python3.8/site-packages/ddns/providers.py", line 182, in update self.update_protocol(protocol) File "/usr/lib/python3.8/site-packages/ddns/pr oviders.py", line 648, in update_protocol output = header.getheader('ddnss-r esponse') AttributeError: 'HTTPMessage' object has no attribute 'getheader'
Comment 1 Stefan Schantl 2020-05-25 16:16:57 UTC 
Fix has been sent to the development mailing list:

https://patchwork.ipfire.org/patch/3133/
Comment 2 Markus Kern 2020-06-06 15:53:07 UTC 
I've applied the fix manuelya - now DDNSS works again!
Comment 3 Peter Müller 2020-10-21 09:50:02 UTC 
For the records: The patch did not seem to make it into any repository.

Resetting this back to ASSIGNED; @all: Please do not forget keeping track of patches on the mailing list(s).
Comment 4 Stefan Schantl 2020-12-02 09:17:27 UTC 
Hello Peter,

thanks for pointing this out.

The fix already has been added upstream for the DDNS Project, but of course did
not get shipped for IPFire yet.

I've created and sent a patch to the development mailing list to push the fix to our users.

https://patchwork.ipfire.org/patch/3690/
Comment 5 Stefan Schantl 2020-12-29 17:08:27 UTC 
Fix has been shipped with Core update 153.