You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are a couple issues related to how forward slashes are handled in search queries on the MAR portal.
The first is that the query, https://mcr.microsoft.com/en-us/catalog?search=dotnet/framework/, produces an error: Sorry, we encountered an error. Please try again later.... The intent is that this query should find repos within the scope of mcr.microsoft.com/dotnet/framework/. Note that if you remove the trailing forward slash, the query works. However, it then does not provide the expected search results. This is the second issue. The forward slash doesn't seem to be interpreted literally. Because in the case of https://mcr.microsoft.com/en-us/catalog?search=dotnet/framework, it's returning back results for Azure Functions which are not within the scope of the dotnet/framework repo and, AFAICT, does not even include the term framework in its content.
There are a couple issues related to how forward slashes are handled in search queries on the MAR portal.
The first is that the query, https://mcr.microsoft.com/en-us/catalog?search=dotnet/framework/, produces an error:
Sorry, we encountered an error. Please try again later...
. The intent is that this query should find repos within the scope ofmcr.microsoft.com/dotnet/framework/
. Note that if you remove the trailing forward slash, the query works. However, it then does not provide the expected search results. This is the second issue. The forward slash doesn't seem to be interpreted literally. Because in the case of https://mcr.microsoft.com/en-us/catalog?search=dotnet/framework, it's returning back results for Azure Functions which are not within the scope of thedotnet/framework
repo and, AFAICT, does not even include the termframework
in its content.Other interesting findings:
The text was updated successfully, but these errors were encountered: