Skip to content

[Feature Request]: Using dev-proxy behind a corporate proxy #917

Closed

Description

@coinzz

Description

The dev-proxy registers as a system-proxy. Therefore our corporate-proxy is not known to the dev-proxy. Our corporate-proxy is essential to use the internet at all. This leads to not having any internet access while the dev-proxy is on. Therefore we mostly can't even reach the parts of our application we would like to test with the dev-proxy.

Expected behaviour

Possibility to configure a corporate-proxy for the dev-proxy and in best case also with a custom authentication.

Dev Proxy Version

0.21.0

Activity

  1. waldekmastykarz commented on Oct 16, 2024

    @waldekmastykarz
    Collaborator

    When starting Dev Proxy, you can use --as-system-proxy false to have it not register itself as a system proxy. Then, you'd need to specify in your app to route its traffic through Dev Proxy. Alternatively, you can use asSystemProxy: false in devproxyrc.json.

  2. coinzz commented on Oct 17, 2024

    @coinzz
    Author

    Ah thank you, we tried that and that did the trick :)
    But unfortunately this option is missing in the schema and therefore not being suggested with auto-completion. I guess we overread the property in devproxy -h, but at least it is listed there.
    Suggestion to maybe add it to the Getting Started section, since otherwise it is also pretty hidden in the Documentation :)

  3. waldekmastykarz commented on Oct 17, 2024

    @waldekmastykarz
    Collaborator

    But unfortunately this option is missing in the schema and therefore not being suggested with auto-completion. I guess we overread the property in devproxy -h, but at least it is listed there.

    Apologies for the oversight! We'll fix it right away.

    Suggestion to maybe add it to the Getting Started section, since otherwise it is also pretty hidden in the Documentation :)

    Let us have a look at how we could best fit it there. Thank you for the suggestions ❤

  4. waldekmastykarz commented on Oct 17, 2024

    @waldekmastykarz
    Collaborator

    I created two separate issues to track your suggestions. I'll close this one.

  5. waldekmastykarz commented on Oct 21, 2024

    @waldekmastykarz
    Collaborator

    @coinzz we've just updated the schema and the changes should be visible immediately. Once again, thank you for pointing it out and sorry for the trouble.

  6. locked and limited conversation to collaborators on Jun 4, 2025
  7. converted this issue into a discussion #1219 on Jun 4, 2025
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

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions