refresh that pagein your first case. If you are accessing the main URL as a GET request, then this is a new conversation.
If you want redirect after GET behavior on your page, you are free to do that. Most people wouldn't want that. In fact, starting a conversation on a GET request is generally not the way you want to go. Most people will have the initial page be in a temporary conversation and only move into a conversation when the user takes some action from that page. I'm not saying it never makes sense to do that, but that's what I would consider the normal best practice.
To clarify, when you say redirect-after-GET, do you mean redirect to the same view but append the
cidrequest parameter to it?
You're right, by refreshing I do mean accessing it through a GET, either by refreshing the page by hitting the browser's refresh button or equivalent.
I can see what you mean where most people wouldn't really need this. (The only reason I'm even considering redirect-after-GET is for efficiency purposes, whereby the queries to populate that page wouldn't be run upon each refresh.)