EPiServer 7 hijacking all requests to aspx with querystring id in it?
Vote:
Hello,
We're working on upgrading one of our sites to EPiServer 7 and just noticed one thing. We have two aspx-pages that are not EPiServer templates of any sort (not inheriting from SimplePage or TemplatePage) and the content of these pages are based on a querystring called "id", maybe not best practice but anyway. Now after upgrading to EPiServer 7 we get the following error message on this page:
Content with id 180846 was not found
Is it so that EPiServer 7 hijacks all requests for aspx-files with querystring "id", even if they are not EPiServer pages? And if so, is there a workaround for this or do we have to change on our side to not use querystring "id"?
Hello,
We're working on upgrading one of our sites to EPiServer 7 and just noticed one thing. We have two aspx-pages that are not EPiServer templates of any sort (not inheriting from SimplePage or TemplatePage) and the content of these pages are based on a querystring called "id", maybe not best practice but anyway. Now after upgrading to EPiServer 7 we get the following error message on this page:
Content with id 180846 was not found
Is it so that EPiServer 7 hijacks all requests for aspx-files with querystring "id", even if they are not EPiServer pages? And if so, is there a workaround for this or do we have to change on our side to not use querystring "id"?
Best regards
Martin