Skip to content

Proxying to IIS Express explained #297

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Mar 8, 2022
Merged

Proxying to IIS Express explained #297

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
4b1e3ea
Proxying to IIS Express explained in Readme.md
Mar 7, 2022
377a47f
Update README.md
josesimoes Mar 8, 2022
b4109df
Merge branch 'develop' into docupdate
josesimoes Mar 8, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -123,6 +123,13 @@ using FileStream fs = new FileStream($"I:\\i-am-a-binary-file.bin", FileMode.Cre
response.Content.ReadAsStream().CopyTo(fs);
```

### Debugging through a reverse proxy

When code is deployed to a MCU it might be desirable to let the device connect to your development machine running IIS Express.
This can be achieved with a proxy such as [this one](https://www.npmjs.com/package/iisexpress-proxy).
Be aware that this leads to SocketExceptions with the current version of **nanoFramework** System.Net.Http when sending consecutive
requests to your development machine. A simple retry mechanism in Debug mode will get around this.

## Feedback and documentation

For documentation, providing feedback, issues and finding out how to contribute please refer to the [Home repo](https://github.com/nanoframework/Home).
Expand Down