• Content count

  • Joined

  • Last visited

About hzr

  • Rank
    New Member

IPS Marketplace

  • Resources Contributor
    Total file submissions: 1
  1. Version 1.0.0


    Overrides outgoing HTTP/S requests to require a proxy. Useful if you are behind a reverse proxy such as Akamai, Blaze, or Incapsula. WARNING: Mail may potentially not be intercepted this way and can leak in headers; consider using a mail service that accepts outgoing messages via HTTPS REST API or run something such as https://www.nginx.com/resources/admin-guide/mail-proxy/ WARNING #2: Ensure curl works and you have an up to date version. If your php curl is broken then IPS will fail back to using sockets or whatever and completely ignore this.


  2. The part you want to protect here is traffic for [china] → [vpn server]. The part you have to trust, and can be exposed is [vpn server] → [final destination site]. It also doesn't need to be 'detecting a VPN' specifically, but most payment providers flag extreme things like 'this ISP does not exist in this billing address country' or 'this city is 6400 km away from this IP's general area'
  3. Migrating from Discourse. Looking for a registration webhook: basically, upon registration, IPB sends a HTTPS POST to my url with parameters like email, user, ip, etc. How difficult would this be to write myself if it doesn't exist? Thanks.