Installing Apidog Microsoft Edge Extension

Browser Extension Limitations and Solutions

Browser security policies impose certain restrictions on extensions, limiting their functionality in specific scenarios. Below are the key limitations and their workarounds.

Restrictions in Browser Extensions

Forbidden Request Header

Some headers, such as Cookie、Host、Origin、Content-Length are automatically blocked by browsers. (View the full list here.).

Cookie Limitations

Cross-origin requests will be blocked from carrying cookies unless CORS credentials support is configured.

Browser extensions cannot directly read or manipulate cookies (including automatically attaching cookies to requests).

Special Request Types

GET/HEADmethods cannot include a request body, and local code/database calls are restricted.

Alternative Solutions

✅ Use Apidog Desktop Client(No restrictions)
✅ Enable Cloud Agent(Bypasses browser limitations)

Installation Guide

Visit the Apidog browser extension page on Microsoft Edge to directly Get the extension.

Permission Settings

Some browser versions require manual permission adjustments, otherwise requests may fail.

FAQs

Why can't I install successfully?

Check if the extension is compatible with your browser version. Try updating Microsoft Edge to resolve the issue.

Why can't certain headers be sent?

Why does a cross-origin request return 403/Forbidden?

Why is the GET request body removed?？

Need to call local code/database？

Learn More

CORS Proxy

Request proxy in Apidog web

Request proxy in shared docs

Request proxy in Apidog client

Installing Apidog Microsoft Edge Extension

Browser Extension Limitations and Solutions#

Restrictions in Browser Extensions#

Alternative Solutions#

Installation Guide#

Permission Settings#

FAQs#

Learn More#