GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — user agent spoofing breaks paypal · Issue #393 · gorhill/httpswitchboard

This repository was archived by the owner on Nov 15, 2017. It is now read-only.
This repository was archived by the owner on Nov 15, 2017. It is now read-only.

user agent spoofing breaks paypal #393

Copy link
Copy link
Open
Open
user agent spoofing breaks paypal#393
Copy link

Description

@anarcat
anarcat
opened on Aug 8, 2014
Issue body actions

When using Paypal, even if I enable all resources in HTTPSB, the page loads then blanks out completely unless I disable user agent spoofing.

Activity

  1. gorhill commented on Aug 8, 2014

    @gorhill
    gorhill
    on Aug 8, 2014
    Owner
    More actions

    Well if the site's behavior depends on the user agent string to be specific values, there is nothing HTTPSB can do. One thing to try is to stick to user agent strings which are close to the real one, i.e do not try to appear as a Firefox or IE browser, stick to user agent strings of Chromium-based browsers.

  2. anarcat commented on Aug 8, 2014

    @anarcat
    anarcat
    on Aug 8, 2014
    Author
    More actions

    well, i wonder if it isn't that the UA changes during the "session" with paypal...

  3. gorhill commented on Aug 8, 2014

    @gorhill
    gorhill
    on Aug 8, 2014
    Owner
    More actions

    What are the UA strings you currently use?

  4. gorhill commented on Aug 8, 2014

    @gorhill
    gorhill
    on Aug 8, 2014
    Owner
    More actions

    The UA string can change during a session. I remember wondering whether I should store the UA for specific pages, and then decided against it. So if it's the source of the problem, I guess I will have to store and reuse it for a page. I think that would be reasonable given that the primary goal is to avoid tracking across many sites, and in any case, a new UA string would be used after leaving the site and coming back after a few minutes.

  5. gorhill commented on Aug 8, 2014

    @gorhill
    gorhill
    on Aug 8, 2014
    Owner
    More actions

    I recommend disabling that option and using "Referer Control", blocking all refers unless an issue occurs, then making exceptions.

    Not recommended to use another add-on which also modifies outbound or inbound headers, as only one extension is allowed to do so, which could undermine HTTPSB's ability to do its job (removing cookie headers, preventing inline javascript execution, etc.)

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

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      You are visitor 01402503 — GeezerVison does not store the pages you look up.
      Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.