Activities of "HadiLoghman"

Hi EngincanV, thanks for reaching out. As I mentioned earlier, our application is .NET Core-based and uses appsettings.json for configuration. Our web.config is minimal and doesn’t include any specific context-related settings. The only notable difference compared to our local environment is that the SelfUrl and Authority in appsettings.json include an additional /api suffix, whereas the AngularUrl does not. This is the only configuration difference we've identified so far. Maybe this helps as well, when I try to change the layout of the website, I get some unexpected results on the staging site. Interestingly, on the first refresh, the website loads normally.

After selecting a different layout After refreshing

The issue doesn't appear to be related to the ServiceProxyScript, as we’re encountering the same error locally as well. We encountered this error for Password change too. This issue happens for all Profile menu items

Hi Team,

We’ve deployed a layered application using ABP. The frontend is implemented in Angular and both the Angular application and the HttpApi.Host (API backend) are hosted on IIS.

• The Angular frontend is hosted at: client.StageDomain.com
• The API (HttpApi.Host) is hosted at: client.StageDomain.com/api

After deploying the API under the /api path on the same domain, we encountered the following issues:

1. The template switcher is not working
2. Change Password functionality fails
3. Several other features are not working as expected, seemingly due to the /api path and the ServiceProxyScript not being loaded

We reviewed the ABP IIS Deployment documentation, but it appears the guidance assumes separate domains or subdomains for each app component.

Thanks,