Skip to content

[Bug]: Telegram silently breaks for response code 400 (Bad request) #205

@gorgobacka

Description

@gorgobacka

Bug Description

While playing around with the new Sparkasse provider, I detected that not all listings are send to Telegram.
After some analysis, I found the issue. Telegram does not like all image urls.

E.g. This image is included in a listing in the Sparkasse provider: https://api.immobilie1.de/estates/31829381/image/278406671/expose-estate-gallery-main-desktop-avif.avif

The image load just fine in a web browser but Telegram does not like it.

Steps to Reproduce

Modify the code to send a message to Telegram with the image URL: https://api.immobilie1.de/estates/31829381/image/278406671/expose-estate-gallery-main-desktop-avif.avif

Expected Behavior

The error is caught and a message is send without an image (sendMessage).

Actual Behavior

No message to Telegram is send and no log message appears. Therefore, the user might miss listings, if he does not check the Fredy UI, carefully.

Screenshots / Logs

Status Code: 400
Text: {"ok":false,"error_code":400,"description":"Bad Request: wrong type of the web page content"}

Environment

Ubuntu

Additional Context

I don't know, if other providers have this problem, too.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions