HTTPS Local Network No Content Case
I have an AspNetCore HttpGet Api that returns
I also have other HttpGet Api that returns contents.
NoContentNoContentI also have other HttpGet Api that returns contents.
1) When the `NoContent` Api is accessed with domain name and https under the same machine where the AspNetCore Web Api is running, I get an error on the browser indicating `ERR_HTTP2_PROTOCOL_ERROR`. And the number is not registered.
This is by accessing the Api on the same machine through chrome with the URL of https://example.com
No option of `Proceed to localhost (unsafe)` is available.1) When the `NoContent` Api is accessed with domain name and https under the same machine where the AspNetCore Web Api is running, I get an error on the browser indicating `ERR_HTTP2_PROTOCOL_ERROR`. And the number is not registered.
This is by accessing the Api on the same machine through chrome with the URL of https://example.com
No option of `Proceed to localhost (unsafe)` is available.2) When the `NoContent` Api is accessed with `localhost` and either http or https under the same machine where the AspNetCore Web Api is running, I do not get an error. And the number is registered.
This is by accessing the Api on the same machine through chrome with the URL of http://localhost
With Https, I first get an `NET::ERR_CERT_COMMON_NAME_INVALID`, but after I clicked `Proceed to localhost (unsafe)`, the number is registered.
This is by accessing the Api on the same machine through chrome with the URL of https://localhost2) When the `NoContent` Api is accessed with `localhost` and either http or https under the same machine where the AspNetCore Web Api is running, I do not get an error. And the number is registered.
This is by accessing the Api on the same machine through chrome with the URL of http://localhost
With Https, I first get an `NET::ERR_CERT_COMMON_NAME_INVALID`, but after I clicked `Proceed to localhost (unsafe)`, the number is registered.
This is by accessing the Api on the same machine through chrome with the URL of https://localhost3) When the Api with content is accessed with domain name and https under the same machine where the AspNetCore Web Api is running, I am able to load the content successfully.
This is by accessing the Api on the same machine through chrome with the URL of https://example.com3) When the Api with content is accessed with domain name and https under the same machine where the AspNetCore Web Api is running, I am able to load the content successfully.
This is by accessing the Api on the same machine through chrome with the URL of https://example.com4) When the `NoContent` Api is accessed with domain name and https under different machine, I do not get an error. And the number is registered.
This is by accessing the Api on a different machine through chrome with the URL of https://example.com
This works either through internet, or on a different machine that connects with the server through PPTP VPN.4) When the `NoContent` Api is accessed with domain name and https under different machine, I do not get an error. And the number is registered.
This is by accessing the Api on a different machine through chrome with the URL of https://example.com
This works either through internet, or on a different machine that connects with the server through PPTP VPN.
