Bug 2082666

Description of problem:
For bucket notification, while creating the topic for the bucket using the aws utility with the push-endpoint URL for "http" endpoint containing the trailing "/" at the end is failed to create the topic.

However, it is working fine if the topic is created without the trailing "/" in the push-endpoint URL.

There is an upstream tracker...[1] for this issue which is fixed in quincy and currently in progress for backport in pacific version. So can we have timeline that when the above fix would be available in the downstream and in which version ?

[1] https://tracker.ceph.com/issues/52738

Version-Release number of selected component (if applicable): RHCS 4.2


Steps to Reproduce:
1. Deploy the RHCS 4.2 cluster with RGW deployed & pubsub,and notification apis enabled
2. Create a new user to create topic and bucket
3. Deploy a simple http server using python http module for notification
4. Create the topic using the below commands.
~~~
$ aws --endpoint-url http://10.74.253.113:8080 sns create-topic --name=mybucket      --attributes='{"push-endpoint": "http://localhost:8900"}'   ## Topic created successfully

$ aws --endpoint-url http://10.74.253.113:8080 sns create-topic --name=mybucket      --attributes='{"push-endpoint": "http://localhost:8900/"}'  ## Failed to create topic
~~~

Actual results:
- When the push-endpoint HTTP URL contains a trailing "/" at the end (ex: http://localhost:8900/ ), topic creation failed

Expected results:
- When the push-endpoint HTTP URL contains a trailing "/" at the end of the push-endpoint URL, topic should be created