Block traffic to trac requests asking for already moved services

[robe]

We are still getting a fair amount of traffic for

mapserver gdal grass

Putting in rules, to redirect these to the respective services.

[robe]

So here are the rules I've put in

I think grass wiki is still active, so just blocked any requests starting with:

/grass/tickets /grass/changesets/, /grass/browser, /grass/export, and redirected these to ​https://github.com/osgeo/grass/

For GDAL, that's completely moved, so redirecting anything starting with /gdal to ​https://gdal.org/

Mapserver has also completely moved so redirected that to ​https://mapserver.org

Geos to ​https://libgeos.org

QGIS ​https://qgis.org

[neteler]

Well, that means we have lost access to the old GRASS GIS tickets... Maybe okay but the tickets weren't moved to GitHub and occasionally serve as a reference.

[robe]

Replying to neteler:

Well, that means we have lost access to the old GRASS GIS tickets... Maybe okay but the tickets weren't moved to GitHub and occasionally serve as a reference.

Okay I've removed the restriction on grass, wasn't aware you still referenced them. I suspect it's all bots just crawling them. Would it be okay to disable crawling on those? Though some bots will ignore the request.

[neteler]

Thanks Regina. Surely disabling bots to continue crawling is fine.

[dbaston]

Would be nice to retain access to GEOS and GDAL tickets as well.

[strk]

Regina where did you put those rules ? I could not find out with a single "git grep" from ansible-deployment

Daniel: I suggest you either file a separate ticket to request recovering access to GEOS and GDAL trac sites, referencing this one, or you re-open this one. If it remains closed as it is it will easily fall off the radars.

[robe]

@strk sorry didn't get around to committing them, they are all committed now in ansible, osgeo7-nginx repo.

[robe]

Replying to dbaston:

Would be nice to retain access to GEOS and GDAL tickets as well.

@dbaston, @Even had explicitly asked us to disable GDAL stuff cause he hated people looking at old docs and stuff. Is there reason you need to see GDAL tickets. I'll reopen the GEOS ones in a bit.

[dbaston]

Thanks @robe. I'll defer to @rouault on the visibility of the GDAL tickets.

[rouault]

yes, read-only access to GDAL Trac tickets could be wishable, as we have had reports of users that were surprised by the redirect to gdal.org (cf ​https://github.com/OSGeo/gdal/issues/11800)

[robe]

Replying to rouault:

yes, read-only access to GDAL Trac tickets could be wishable, as we have had reports of users that were surprised by the redirect to gdal.org (cf ​https://github.com/OSGeo/gdal/issues/11800)

Done