Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Telegram inbox: images (photo) not shown (HTTP 302 problem) #782

Open
povesma opened this issue May 20, 2024 · 1 comment
Open

Telegram inbox: images (photo) not shown (HTTP 302 problem) #782

povesma opened this issue May 20, 2024 · 1 comment

Comments

@povesma
Copy link

povesma commented May 20, 2024

Describe the bug
I'm running an on-premise Chatwoot server (3.9.0).

When an image is sent from Chatwoot to Telegram bot inbox (I suspect, it also applies to other inboxes), the image is not visible in a mobile app (Android, v. 1.10.37, also seen on iOS app). Web-server receives a request (/rails/active_storage/representations/redirect/{base64-encoded-json}--some_id/file_444.jpg), and returns HTTP 302 with a location like

/rails/active_storage/disk/{blah-blah}/file_444.jpg

To Reproduce

Send an image from the mobile app to a Telegram bot inbox. Image placeholder appears in the chat as a white rectangle, but no image is visible. On web all is good - image is visible

Expected behavior

Image is visible

Environment

  • A self hosted installation of Chatwoot 3.8.0 in docker
  • Chatwoot Mobile App Version: 1.10.37 for Android

Possible fixes

I think, that the issue is in handling redirect (302). I reconfigured by Nginx to intercept and handle 302 and return the actual content of 'location' instead of returning 302, and the problem gone.

Copy link

linear bot commented May 20, 2024

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant