How can I redirect invalid page requests to the Space Home Page instead of a 404 error returned?

Question

I have recently migrated an on-premise Confluence Wiki server containing a handful of spaces via the space export / import functionality and that process went relatively well for the most part. We're facing a challenge in trying to perform a simple URL redirect of non-existent pages that return a 404 status.

Is it possible to customize the 404 error page to just simply redirect to the space overview page instead?

The reason behind the ask is that we have an external web application server that references the Confluence cloud wiki URL that dynamically generates a URI based on the context.

ie) https://sitename.atlassian.net/wiki/spaces/SPACEKEY/overview/a/b/c should redirect to https://sitename.atlassian.net/wiki/spaces/SPACEKEY/overview/ instead a 404 not found error.

I have looked through the documentation and the available plug-ins but haven't found anything obvious.

Is this even possible or is my only option to use an external reverse proxy solution?

Thanks.

Andrew_tyqp4k · Answer

Hi Charlie,

Thanks for your response. Unfortunately we have no control over the web application to make those changes (the URLs get dynamically generated based on a leading URL which is configurable... that's it). We previously had the on-premise Confluence server running and we used a plug-in called the Advanced Redirection Plugin by hasCode.com - http://app.hascode.com/advanced-redirection-plugin/ which got the job done. The plugin hasn't been actively maintained for a long time and is not compatible with Confluence Cloud. I haven't found anything that provides any equivalence within the Atlassian marketplace eco-system yet.

Charlie Misonne · Answer

Hi Andrew,

Confluence will reply with a 404 when something does not exist which is the proper http reply for this. Changing these kinds of technical requirements are usually not possible on the Atlassian Cloud ecosystem.

You can try a reverse proxy but personally I never tried it in front of a Atlassian Cloud application so I'm not sure it will work.

Do you have any control over the web application? Perhaps you could truncate the URL when Confluence replies with a 404.