Rocket.Chat icon indicating copy to clipboard operation
Rocket.Chat copied to clipboard

Channel named "." cannot be joined

Open Gummikavalier opened this issue 1 year ago • 4 comments

Description:

Channel called . can be created but it cannot be joined or returned after navigating away from it.

Just a stupid issue we encountered, but nevertheless it is best to report it. It might indicate some other issue with escaping channel names etc.

Steps to reproduce:

  1. Create a public channel called . with web client
  2. Search for the channel with another user and try to join the channel

Expected behavior:

You can join the channel as usual

Actual behavior:

Screenshot from 2024-12-12 19-03-19

In the url-bar the channel path shows as /channel/ and not /channel/.

Typing in the correct url does not have any effect, as the address turns into /channel/ again.

Server Setup Information:

  • Version of Rocket.Chat Server: 7.1.0
  • License Type: Enterprise
  • Number of Users: 500+
  • Operating System: RHEL8
  • Deployment Method: tar
  • Number of Running Instances: 4
  • DB Replicaset Oplog: Yes
  • NodeJS Version: 20.18.0
  • MongoDB Version: 6.0

Client Setup Information

  • Desktop App or Browser Version: Any browser

Gummikavalier avatar Dec 12 '24 17:12 Gummikavalier

I believe room names containing special characters, such as (.), should not be allowed.

thepiyush-303 avatar Dec 12 '24 17:12 thepiyush-303

This will be one for the internal team.

I will refer it immediately.

reetp avatar Dec 13 '24 11:12 reetp

Yes, the issue is correct. I rechecked it. we can create this channel, but even admin cannot open it. Other user can leave it but not open it. The channel . appears in the list, and backend operations like leaving the channel work, suggesting the database recognizes it Clicking on the channel results in Page not found affecting both admins and users. Likely cause: a routing issue where . is misinterpreted as a relative path in URLs or a validation gap allowing invalid channel names.

darshanlahamage avatar Dec 14 '24 11:12 darshanlahamage

Yes, the issue is correct. I rechecked it.

I know hence:

This will be one for the internal team. I will refer it immediately.

No further action required.

reetp avatar Dec 14 '24 12:12 reetp