UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.84 Safari/537.36

Steps to reproduce the problem:
1. define opensearch.xml to something shown in this stackoverflow post
https://stackoverflow.com/questions/47845873/forward-slashes-in-searchterms-break-search-url-in-opensearch-xml
1. site uses search template something like "https://somesite.com/search/{searchTerms}/page/1"
2. try search for 'this/that'
3. the search request goes to target site as https://somesite.com/search/this/that/page/1

What is the expected behavior?
the search request should have gone as https://somesite.com/search/this%2fthat/page/1

What went wrong?
as per the opensearch specification mentioned in http://www.opensearch.org/Specifications/OpenSearch/1.1#The_.22searchTerms.22_parameter
==========

The searchTerms should be url encoded. 

=========

This works fine when the searchTerm is passed as a query param. But the same doesn't work if the search param is passed as part of an URL.

Did this work before? No 

Chrome version: 63.0.3239.84  Channel: stable
OS Version: 10.0
Flash Version: Shockwave Flash 28.0 r0

The following is the stackoverflow question for the same issue.

https://stackoverflow.com/questions/47845873/forward-slashes-in-searchterms-break-search-url-in-opensearch-xml