Skip to content

Referrer-Policy changes within the .htaccess file will not be applied. #14374

Closed

Description

@iPaat

Referrer-Policy changes within the .htaccess file will not be applied.

Steps to reproduce

  1. Change referrer policy in your .htaccess file from no-referrer to strict-origin-when-cross-origin.
Header set Referrer-Policy "strict-origin-when-cross-origin"
  1. Place somewhere a .php file on a webserver with the following contents:
<?php

var_dump($_SERVER);
  1. Use the browser development tools to place a link on DOMAIN.TLD/login which points to your .php file on your webserver.
  2. Click on that link and search for the HTTP_REFERER key in the output that the .php file you created produces.

Expected behaviour

You should be able to see the HTTP_REFERER field.

Actual behaviour

There is no HTTP_REFERER field.

Server configuration

Operating system:
Linux

Web server:
Apache

Nextcloud version: (see Nextcloud admin page)
15.0.4

Signing status:

Signing status
No errors have been found.

Are you using encryption: yes

Client configuration

Browser:
Firefox 66.0b10 & 65.0.1
Chrome 72.0.3626.119

Operating system:
Windows

Activity

  1. added
    0. Needs triagePending check for reproducibility or if it fits our roadmap
    on Feb 25, 2019
  2. kesselb commented on Feb 25, 2019

    @kesselb
    Contributor

    How is this related to nextcloud?

  3. DominikWA commented on Feb 25, 2019

    @DominikWA
    Member

    I had the same problem, after a quick digging in I found out that there are meta tags that also sets the referral-policy. Here you can find my fix #14318.

    Best,
    Dominik

  4. kesselb commented on Feb 25, 2019

    @kesselb
    Contributor

    I had the same problem, after a quick digging in I found out that there are meta tags that also sets the referral-policy. Here you can find my fix #14318.

    This could be the reason 👍

  5. iPaat commented on Feb 25, 2019

    @iPaat
    MemberAuthor

    This helped, thanks a lot.

    Hopefully it will be merged soon so that my source code doesn't deviate from the original.

    Are there any security risks if I remove the meta tags as suggested?

  6. added this to the Nextcloud 14.0.10 milestone on Feb 28, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    0. Needs triagePending check for reproducibility or if it fits our roadmapbug

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions