Base solution for your next web application
Ends in:
01 DAYS
01 HRS
01 MIN
01 SEC

Activities of "yoshrepublic"

Thank you

Thank you. I have added the below class to the web.core layer and the interface to the core layer. It works like a charm. My only question is should I be using ISingletonDependency instead?

` class AppContextAccessor: IAppContextAccessor, ITransientDependency { private readonly IHttpContextAccessor _httpContextAccessor;

    public AppContextAccessor(IHttpContextAccessor contextAccessor)
    {
        _httpContextAccessor = contextAccessor;
    }

    public string GetIpAddress()
    {
        var httpContext = _httpContextAccessor.HttpContext;
        return httpContext.Connection.RemoteIpAddress.ToString();
    }

    public string GetBrowserInfo()
    {
        var httpContext = _httpContextAccessor.HttpContext;
        return httpContext.Request.Headers["User-Agent"].ToString();
    }
}`

Below is what's at the end of the logfile. I have tried in incognito window or different browser with no luck.

INFO 2019-06-18 12:12:29,182 [5 ] soft.AspNetCore.Hosting.Internal.WebHost - Request starting HTTP/1.1 DEBUG http://localhost:22742/ 0 INFO 2019-06-18 12:12:29,182 [4 ] soft.AspNetCore.Hosting.Internal.WebHost - Request starting HTTP/1.1 GET http://localhost:22742/
INFO 2019-06-18 12:12:29,259 [5 ] soft.AspNetCore.Hosting.Internal.WebHost - Request finished in 80.3749ms 200 INFO 2019-06-18 12:12:29,304 [4 ] tion.Cookies.CookieAuthenticationHandler - Identity.Application was not authenticated. Failure message: Unprotect ticket failed INFO 2019-06-18 12:12:29,668 [8 ] soft.AspNetCore.Hosting.Internal.WebHost - Request finished in 491.5018ms 404 INFO 2019-06-18 12:14:32,889 [19 ] soft.AspNetCore.Hosting.Internal.WebHost - Request starting HTTP/1.1 GET http://localhost:22742/
INFO 2019-06-18 12:14:32,895 [19 ] soft.AspNetCore.Hosting.Internal.WebHost - Request finished in 6.3843ms 404

Thank you

Wow. These have got to be the worst non-answers I have ever gotten back from a support team.

Do it as you do for your other websites? Seriously?

If you don't know what a DNS record or the world's largest domain registry is, you probably shouldn't be answering technical questions.

I have done my homework and tried to find documentation on publishing and implement your public site but only found scattered bits and pieces. I did not ask you to fix code that I wrote or broke. I have asked instructions on how to use your product in the most common scenario I can think of.

So here it is again:

I have a typical setup on Azure with three app services:

mydomainAPI.azurewebsites.net (.Net core 6.5) mydomainUi.azurewebsites.net (Angular 6.5) mydomainPublic.azurewebsites.net (MVC Public ASPNETZERO site)

The public site is only used for the home page. All other pages will be handled by Angular

  1. What steps do I need to make to publish and implement the PUBLIC site in Azure (similar to your Angular documentation)?
  2. The steps should include all application settings changes in the public project showing the app service domains as well as settings that need to be changed in the other two projects if needed.
  3. What DNS records are required to make this all work with the browser only showing mydomain.com?

Hello,

Thank you for your response. I understand that I could create a separate Angular solution for the public pages but what I really need fast loading home page withot all the Angular overhead. My questions were more about implementing your public solution in a fairly typical scenaro that I have and most likely others too. Can you lay out how I would go about implementing your public site and answer my bolded questions please?

Awesome. That worked. Thank you

I have fat-fingered my own redirect. My apologies :(

Showing 1 to 8 of 8 entries