Anchors/Fragements not maintained after auto-correction

Puhhh... that's in correct.

The module only takes the 301 redirect url and if this does not provide the anchors/fragments it get's removed. I'm not sure if it's correct to maintain the anchors/fragments if they are not in the 301. It may be useful if you change your site structure without changing your content. If we keep the anchors/fragments on automatic updates it will fail later as the anchors/fragments is now also verified since v1.1. This means we could add this as a new feature. Can you share a patch, please?

I'd like to hear some others if this is the way how it should work (design wise) as I'm not sure... what are web browsers doing here with the anchors/fragments?

Mainly I need to know what browsers are doing. Fragments a a bit special. If browser will not keep the fragment on redirects I may not implement it in linkchecker, too. Otherwise if they do, we should also keep the fragment in linkchecker, too.

Patch attached (untested)

And now without tabs.

And now without tabs.

Any news on your test results?

I tested the latest patch, and fragments were not being appended to the end of the new URL.

The test was a drush script with the logic from that patch, with an example old URL and new URL:

#!/usr/bin/env drush
<?php
$old_link_fqdn = 'http://example.com/path#fragment';
$new_link_fqdn = 'http://example.com/new-path';

$old_link_fqdn_options = drupal_parse_url($old_link_fqdn);
$new_link_fqdn_options = drupal_parse_url($new_link_fqdn);
$new_link_fqdn_options['fragment'] = $old_link_fqdn_options['fragment'];
$new_link_fqdn_options['absolute'] = TRUE;
$new_link_fqdn = url($new_link_fqdn_options['path'], $new_link_fqdn_options);

drupal_set_message(print_r($old_link_fqdn_options,1));
drupal_set_message($new_link_fqdn);

And the output shows a failure to add the fragment to the end of the new URL:

Array
(
    [path] => http://example.com/path#fragment
    [query] => Array
        (
        )
    [fragment] =>
)

http://example.com/new-path

So I have attached my own patch which has been tested locally to have "#", and everything afterward, persist in the new URL. I'm submitting the patch to be reviewed by the community.