Skip to content

Add recommended virtual directory setup to docs #175

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.

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 2 commits into from
Aug 30, 2022

Conversation

twsouthwick
Copy link
Member

@twsouthwick twsouthwick commented Aug 26, 2022

Virtual directories must be the same between the core and framework app. This may not be obvious to users as they get started, but a number of issues have been filed around this. This change adds some docs to guide people to this.

Fixes #174

Copy link
Contributor

@gumbarros gumbarros left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In docs/diagnostics.md

# Diagnostics

There is an initial system to help diagnose commone issues that can be opted into. Currently, this is only available on the ASP.NET Framework application

There is a typo, the correct is "commons" instead of "commone" right?

@twsouthwick twsouthwick force-pushed the tasou/add-diagnostics branch from 8252a48 to afe96d6 Compare August 26, 2022 20:08
@twsouthwick twsouthwick changed the title Add diagnostic to verify virtual directory setup Add recommended virtual directory setup to docs Aug 26, 2022
@twsouthwick
Copy link
Member Author

Removing the diagnostic code for now in favor of going down a more generalized approach for health checks: #176

@twsouthwick twsouthwick force-pushed the tasou/add-diagnostics branch from afe96d6 to df24bac Compare August 26, 2022 20:12
@twsouthwick twsouthwick requested a review from gumbarros August 26, 2022 22:41
Copy link
Contributor

@gumbarros gumbarros left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we specify the two applications must be on different sites to prevent my issues on #174 ?

Recomendation: Ensure your two applications have the same virtual directory path and are hosted on different websites.

@twsouthwick
Copy link
Member Author

@gumbarros good catch. I've updated the recommendation

@twsouthwick twsouthwick enabled auto-merge (squash) August 29, 2022 19:58
@twsouthwick
Copy link
Member Author

@mjrousos @Tratcher can I get someone with write access to approve this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

AddProxySupport on .NET Framework not working with UseForwardedHeaders
3 participants