• Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      NOTE: This suggestion is for Confluence Cloud. Using Confluence Server? See the corresponding suggestion.

      It would be great if you could bookmark the results of a search.

      The obvious solution of making searches a GET request rather than a POST won't work. This is because non-ASCII characters can't be reliably included in a URL, breaking searching for many of our users.

      The proper way to implement this is to store searches in Confluence with an identifier. The permalink for a search is then simply a link to repeat the saved search.

      This is part of the Smart Lists feature, which incorporates other improvements to searching.

            [AI-655] Allow search results to be bookmarked

            Searches use a GET now. They still can't be persisted in the UI, but this is good enough to support bookmarking.

            Matt Ryall added a comment - Searches use a GET now. They still can't be persisted in the UI, but this is good enough to support bookmarking.

            Matt - this can be closed now, right? Seems to work fine for me..

            Sherif Mansour added a comment - Matt - this can be closed now, right? Seems to work fine for me..

            You couldn't redirect to the permanent URL that identifies the search with an identifier?

            Unfortunately, we can't. Searches can't currently be persisted. As you suspected, implementing persistence for searches is called "smart lists", CONF-6453.

            Scott's suggestion might work, but we still have several application servers which we're unable to configure to use UTF-8 URL encoding. Resin 3 on confluence.atlassian.com is a case in point.

            Matt Ryall added a comment - You couldn't redirect to the permanent URL that identifies the search with an identifier? Unfortunately, we can't. Searches can't currently be persisted. As you suspected, implementing persistence for searches is called "smart lists", CONF-6453 . Scott's suggestion might work, but we still have several application servers which we're unable to configure to use UTF-8 URL encoding. Resin 3 on confluence.atlassian.com is a case in point.

            Simon Lieschke added a comment - - edited

            Simon, thanks for the suggestion. We already use this pattern in many places in Confluence. The back button works on the search page in Confluence 2.7 and above without using that pattern because we removed the no-store caching header.

            Yeah, I found this issue via the blog post in question

            This request is to make the searches "bookmarkable", by giving them a permanent URL. Unfortunately, the redirect-to-GET-after-POST doesn't help us here.

            The Wikipedia page notes the pattern helps applications to behave more intuitively with browser bookmarks. You couldn't redirect to the permanent URL that identifies the search with an identifier? Or is the idea that you can only link to a saved smart list (possibly because you don't want to persist the search criteria for every search performed)?

            Simon Lieschke added a comment - - edited Simon, thanks for the suggestion. We already use this pattern in many places in Confluence. The back button works on the search page in Confluence 2.7 and above without using that pattern because we removed the no-store caching header. Yeah, I found this issue via the blog post in question This request is to make the searches "bookmarkable", by giving them a permanent URL. Unfortunately, the redirect-to-GET-after-POST doesn't help us here. The Wikipedia page notes the pattern helps applications to behave more intuitively with browser bookmarks . You couldn't redirect to the permanent URL that identifies the search with an identifier? Or is the idea that you can only link to a saved smart list (possibly because you don't want to persist the search criteria for every search performed)?

            I think that we should just move all URL parsing to be UTF-8, and check in the setup that this is correct. Then we can use GETs properly.

            As most people use the standalone configuration, this should be setup already (in the standalone). For other application servers, we would need to provide instructions.

            Scott Farquhar added a comment - I think that we should just move all URL parsing to be UTF-8, and check in the setup that this is correct. Then we can use GETs properly. As most people use the standalone configuration, this should be setup already (in the standalone). For other application servers, we would need to provide instructions.

            Matt Ryall added a comment -

            Simon, thanks for the suggestion. We already use this pattern in many places in Confluence. The back button works on the search page in Confluence 2.7 and above without using that pattern because we removed the no-store caching header.

            This request is to make the searches "bookmarkable", by giving them a permanent URL. Unfortunately, the redirect-to-GET-after-POST doesn't help us here.

            Matt Ryall added a comment - Simon, thanks for the suggestion. We already use this pattern in many places in Confluence. The back button works on the search page in Confluence 2.7 and above without using that pattern because we removed the no-store caching header . This request is to make the searches "bookmarkable", by giving them a permanent URL. Unfortunately, the redirect-to-GET-after-POST doesn't help us here.

            Have a look at the redirect after POST pattern.

            Simon Lieschke added a comment - Have a look at the redirect after POST pattern .

              Unassigned Unassigned
              matt@atlassian.com Matt Ryall
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: