X Tutup
Skip to content

fix: Normalize URL before executing HTTP request#13674

Open
akylkb wants to merge 1 commit intochatwoot:developfrom
akylkb:patch-1
Open

fix: Normalize URL before executing HTTP request#13674
akylkb wants to merge 1 commit intochatwoot:developfrom
akylkb:patch-1

Conversation

@akylkb
Copy link

@akylkb akylkb commented Feb 27, 2026

Support for Unicode characters, such as Cyrillic

Support for Unicode characters, such as Cyrillic
@akylkb akylkb changed the title Normalize URL before executing HTTP request fix: Normalize URL before executing HTTP request Feb 27, 2026
@nestordavalos
Copy link
Contributor

Hi, I reviewed this PR and noticed that the case it's trying to solve is already covered in the current codebase.

SafeEndpointValidatable has a validate_no_unicode_chars method that rejects URLs with non-ASCII characters in the hostname at save time. A domain with Cyrillic characters would never reach execute_http_request.

The only scenario where Unicode could appear in the final URL would be through Liquid templates (when the LLM injects values into path segments), but that's already handled by the rescue StandardError in perform without causing a crash.

Could you maybe share a concrete use case where this actually fails? That way we can better understand if there's a scenario I'm not considering.

CC: aakashb95

@sojan-official sojan-official added the community PRs from the community label Mar 5, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

community PRs from the community

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

X Tutup