Skip to main content

Fetching User IP Address And Geolocation In Blazor WebAssembly

In this article, we are going to fetch user public IP Addresses and Geolocation in the blazor webassembly application.

Third-Party APIs:

The API to get users IP Address endpoint:
https://jsonip.com/
Free endpoint, for official docs, visit "https://getjsonip.com/#docs".

The API to get users Geolocation based on users IP Address endpoint:
http://api.ipstack.com/User_IP?access_key=your_api_key&format=1
This endpoint has pricing subscription plans including the free subscription plan, for official docs, visit: "https://ipstack.com/"

Create A Sample Blazor WebAssembly:

Let's begin our demo by creating a sample Blazor WebAssembly application. For development, any type of IDE can be used but more recommended are Visual Studio 2019(Version 16.8.* latest that builds .Net5) or Visual Studio Code.

Fetch User IP Address:

Now let's create a model that represents the IP Address payload.
Models/IPAddress.cs:
using System.Text.Json.Serialization;

namespace Blwasm.IPGeolocation.Models
{
  public class IPAddress
  {
   [JsonPropertyName("ip")]
   public string IP{get;set;}

   [JsonPropertyName("geo-ip")]
   public string GeoIP{get;set;}

   [JsonPropertyName("API Help")]
   public string APIHelp{get;set;}
  }
}
  • The 'JsonPropertyName' attribute to map the payload parameters to c# class properties. This 'JsonPropertyName' attribute loads from the 'System.Text.Json.Serialization'
Now install an HTTP extension package that helps to register the named HTTP clients.
Package Manager
Install-Package Microsoft.Extensions.Http -Version 5.0.0
.Net CLI
dotnet add package Microsoft.Extensions.Http --version 5.0.0
Register HttpClient with IP Address base domain using named HTTP client technique.
Program.cs:
builder.Services.AddHttpClient("IP",(options) => {
  options.BaseAddress = new Uri("https://jsonip.com");
});
  • Here we register HTTP Client with the name "IP". This name should be used for creating an HTTP client object from the HttpClientFactory.
Now implement logic to fetch the IP Address API by creating a service file.
Services/IApiClietService.cs:
using System.Threading.Tasks;
using Blwasm.IPGeolocation.Models;

namespace Blwasm.IPGeolocation.Services
{
  public interface IApiClientService
  {
   Task<IPAddress> GetUserIPAsync();
  }
}
Services/ApiClientService.cs:
using System.Net.Http;
using System.Net.Http.Json;
using System.Threading.Tasks;
using Blwasm.IPGeolocation.Models;

namespace Blwasm.IPGeolocation.Services
{
  public class ApiClientService: IApiClientService
  {
   private readonly IHttpClientFactory _httpClientFactory;

   public ApiClientService(IHttpClientFactory httpClientfactory)
   {
	_httpClientFactory = httpClientfactory;
   }

   public async Task<IPAddress> GetUserIPAsync()
   {
   var client =  _httpClientFactory.CreateClient("IP");
   return await client.GetFromJsonAsync<IPAddress>("/");
   }
  }
}
  • (Line: 12) Injected the HttpClientFacotry.
  • (Line: 19) Creating an HTTP Client object from the HttpClientFacotry by inputting the name "IP".
  • (Line: 20) Invoking the API and converting the response to 'IPAddress' type with the help of an extension method like 'GetFromJsonAsync<>' that loads from System.Net.Http.Json. Here we passed the "/" as a path because domain itself returning the IP Address results.
Register these client call service to support the dependency injection.
Program.cs:
builder.Services.AddScoped<IApiClientService,ApiClientService>();
Now update the Index.razor page to display the user's IP Address.
Pages/Index.razor:(Html Part)
@page "/"
@inject IApiClientService _apiClientService;

<div>
 <h4>User Ip - @ipAddress.IP</h4>
</div>
  • Here using razor syntax injecting the 'IApiClientService'
Pages/Index.razor:(Code Part)
@code{
    IPAddress ipAddress = new IPAddress();
    protected override async  Task OnInitializedAsync()
    {
        ipAddress =  await _apiClientService.GetUserIPAsync();
    }
}
  • Inside of the lifecycle method like 'OnInitializedAsyn()' invoking the IP Address API call.

Fetch User's Geolocation:

Now let's create a payload model for the Geolocation API(HTTP://api.ipstack.com)
Models/UserGeolocation.cs:
using System;
using System.Collections.Generic;

namespace Blwasm.IPGeolocation.Models
{
    public class Language
    {
        public string code { get; set; }
        public string name { get; set; }
        public string native { get; set; }
    }

    public class Location
    {
        public int? geoname_id { get; set; }
        public string capital { get; set; }
        public List<Language> languages { get; set; }
        public string country_flag { get; set; }
        public string country_flag_emoji { get; set; }
        public string country_flag_emoji_unicode { get; set; }
        public string calling_code { get; set; }
        public bool? is_eu { get; set; }
    }

    public class TimeZone
    {
        public string id { get; set; }
        public DateTime current_time { get; set; }
        public int? gmt_offset { get; set; }
        public string code { get; set; }
        public bool is_daylight_saving { get; set; }
    }

    public class Currency
    {
        public string code { get; set; }
        public string name { get; set; }
        public string plural { get; set; }
        public string symbol { get; set; }
        public string symbol_native { get; set; }
    }

    public class Connection
    {
        public int? asn { get; set; }
        public string isp { get; set; }
    }

    public class Security
    {
        public bool is_proxy { get; set; }
        public object proxy_type { get; set; }
        public bool is_crawler { get; set; }
        public object crawler_name { get; set; }
        public object crawler_type { get; set; }
        public bool is_tor { get; set; }
        public string threat_level { get; set; }
        public object threat_types { get; set; }
    }

    public class UserGeoLocation
    {
        public string ip { get; set; }
        public string hostname { get; set; }
        public string type { get; set; }
        public string continent_code { get; set; }
        public string continent_name { get; set; }
        public string country_code { get; set; }
        public string country_name { get; set; }
        public string region_code { get; set; }
        public string region_name { get; set; }
        public string city { get; set; }
        public string zip { get; set; }
        public double? latitude { get; set; }
        public double? longitude { get; set; }
        public Location location { get; set; }
        public TimeZone time_zone { get; set; }
        public Currency currency { get; set; }
        public Connection connection { get; set; }
        public Security security { get; set; }
    }

}
Now register the HTTP client for the geolocation API
Program.cs:
builder.Services.AddHttpClient("Location", options => {
  options.BaseAddress = new Uri("http://api.ipstack.com");
});
  • Registered the geolocation API with the name 'Location'.
Implement logic for the geolocation API call.
Services/IApiClientService.cs:
Task<UserGeoLocation> GetLocationAsync(string userIp);
Services/ApiClientService.cs:
public async Task<UserGeoLocation> GetLocationAsync(string userIp)
{
	string path = $"{userIp}?access_key=Your_Secured_Key";
	var client = _httpClientFactory.CreateClient("Location");
	return await client.GetFromJsonAsync<UserGeoLocation>(path);
}
  • Here URL is made of the User Ip address and API secured key that's will get once registered with "HTTP://ipstack.com".
  • Creating the HTTP client object by using the name "Location" from the HttpClientFactory.
Now update the Index.razor page to display the geolocation data.
Pages/Index.razor:(Html Part)
<div>
 <h4>User Ip - @ipAddress.IP</h4>
 <ul>
     <li>Country - @location.country_name</li>
     <li>Regionname - @location.region_name</li>
     <li>City - @location.city</li>
 </ul>
</div>
Pages/Index.razor:(Code Part)
@code{
    IPAddress ipAddress = new IPAddress();
    UserGeoLocation location = new UserGeoLocation();
    protected override async  Task OnInitializedAsync()
    {
        ipAddress =  await _apiClientService.GetUserIPAsync();
        location = await _apiClientService.GetLocationAsync(ipAddress.IP);
    }
}
That's all about the fetching User IP Address and Geolocation in the blazor webassembly application.

Support Me!
Buy Me A Coffee PayPal Me

Wrapping Up:

Hopefully, I think this article delivered some useful information about fetching user IP Addresses and Geolocation in the Blazor Application. I love to have your feedback, suggestions, and better techniques in the comment section below.

Refer:

Follow Me:

Comments

Popular posts from this blog

Angular 14 Reactive Forms Example

In this article, we will explore the Angular(14) reactive forms with an example. Reactive Forms: Angular reactive forms support model-driven techniques to handle the form's input values. The reactive forms state is immutable, any form filed change creates a new state for the form. Reactive forms are built around observable streams, where form inputs and values are provided as streams of input values, which can be accessed synchronously. Some key notations that involve in reactive forms are like: FormControl - each input element in the form is 'FormControl'. The 'FormControl' tracks the value and validation status of form fields. FormGroup - Track the value and validate the state of the group of 'FormControl'. FormBuilder - Angular service which can be used to create the 'FormGroup' or FormControl instance quickly. Form Array - That can hold infinite form control, this helps to create dynamic forms. Create An Angular(14) Application: Let'

.NET 7 Web API CRUD Using Entity Framework Core

In this article, we are going to implement a sample .NET 7 Web API CRUD using the Entity Framework Core. Web API: Web API is a framework for building HTTP services that can be accessed from any client like browser, mobile devices, and desktop apps. In simple terminology API(Application Programming Interface) means an interface module that contains programming functions that can be requested via HTTP calls either to fetch or update data for their respective clients. Some of the Key Characteristics of API: Supports HTTP verbs like 'GET', 'POST', 'PUT', 'DELETE', etc. Supports default responses like 'XML' and 'JSON'. Also can define custom responses. Supports self-hosting or individual hosting, so that all different kinds of apps can consume it. Authentication and Authorization are easy to implement. The ideal platform to build the REST full services. Install The SQL Server And SQL Management Studio: Let's install the SQL server on our l

ReactJS(v18) JWT Authentication Using HTTP Only Cookie

In this article, we will implement the ReactJS application authentication using the HTTP-only cookie. HTTP Only Cookie: In a SPA(Single Page Application) Authentication JWT token either can be stored in browser 'LocalStorage' or in 'Cookie'. Storing the JWT token inside of the cookie then the cookie should be HTTP Only. The HTTP-ONly cookie nature is that it will be only accessible by the server application. Client apps like javascript-based apps can't access the HTTP-Only cookie. So if we use the authentication with HTTP-only JWT cookie then we no need to implement the custom logic like adding authorization header or storing token data, etc at our client application. Because once the user authenticated cookie will be automatically sent to the server by the browser on every API call. Authentication API: To authenticate our client application with JWT HTTP-only cookie, I developed a NetJS(which is a node) Mock API. Check the GitHub link and read the document on G

.NET6 Web API CRUD Operation With Entity Framework Core

In this article, we are going to do a small demo on AspNetCore 6 Web API CRUD operations. What Is Web API: Web API is a framework for building HTTP services that can be accessed from any client like browser, mobile devices, desktop apps. In simple terminology API(Application Programming Interface) means an interface module that contains a programming function that can be requested via HTTP calls to save or fetch the data for their respective clients. Some of the key characteristics of API: Supports HTTP verbs like 'GET', 'POST', 'PUT', 'DELETE', etc. Supports default responses like 'XML' and 'JSON'. Also can define custom responses. Supports self-hosting or individual hosting, so that all different kinds of apps can consume it. Authentication and Authorization are easy to implement. The ideal platform to build REST full services. Create A .NET6 Web API Application: Let's create a .Net6 Web API sample application to accomplish our

Angular 14 State Management CRUD Example With NgRx(14)

In this article, we are going to implement the Angular(14) state management CRUD example with NgRx(14) NgRx Store For State Management: In an angular application to share consistent data between multiple components, we use NgRx state management. Using NgRx state helps to avoid unwanted API calls, easy to maintain consistent data, etc. The main building blocks for the NgRx store are: Actions - NgRx actions represents event to trigger the reducers to save the data into the stores. Reducer - Reducer's pure function, which is used to create a new state on data change. Store - The store is the model or entity that holds the data. Selector - Selector to fetch the slices of data from the store to angular components. Effects - Effects deals with external network calls like API. The effect gets executed based the action performed Ngrx State Management flow: The angular component needs data for binding.  So angular component calls an action that is responsible for invoking the API call.  Aft

Angular 14 Crud Example

In this article, we will implement CRUD operation in the Angular 14 application. Angular: Angular is a framework that can be used to build a single-page application. Angular applications are built with components that make our code simple and clean. Angular components compose of 3 files like TypeScript File(*.ts), Html File(*.html), CSS File(*.cs) Components typescript file and HTML file support 2-way binding which means data flow is bi-directional Component typescript file listens for all HTML events from the HTML file. Create Angular(14) Application: Let's create an Angular(14) application to begin our sample. Make sure to install the Angular CLI tool into our local machine because it provides easy CLI commands to play with the angular application. Command To Install Angular CLI npm install -g @angular/cli Run the below command to create the angular application. Command To Create Angular Application ng new name_of_your_app Note: While creating the app, you will see a noti

Unit Testing Asp.NetCore Web API Using xUnit[.NET6]

In this article, we are going to write test cases to an Asp.NetCore Web API(.NET6) application using the xUnit. xUnit For .NET: The xUnit for .Net is a free, open-source, community-focused unit testing tool for .NET applications. By default .Net also provides a xUnit project template to implement test cases. Unit test cases build upon the 'AAA' formula that means 'Arrange', 'Act' and 'Assert' Arrange - Declaring variables, objects, instantiating mocks, etc. Act - Calling or invoking the method that needs to be tested. Assert - The assert ensures that code behaves as expected means yielding expected output. Create An API And Unit Test Projects: Let's create a .Net6 Web API and xUnit sample applications to accomplish our demo. We can use either Visual Studio 2022 or Visual Studio Code(using .NET CLI commands) to create any.Net6 application. For this demo, I'm using the 'Visual Studio Code'(using the .NET CLI command) editor. Create a fo

Part-1 Angular JWT Authentication Using HTTP Only Cookie[Angular V13]

In this article, we are going to implement a sample angular application authentication using HTTP only cookie that contains a JWT token. HTTP Only JWT Cookie: In a SPA(Single Page Application) Authentication JWT token either can be stored in browser 'LocalStorage' or in 'Cookie'. Storing JWT token inside of the cookie then the cookie should be HTTP Only. The HTTP-Only cookie nature is that it will be only accessible by the server application. Client apps like javascript-based apps can't access the HTTP-Only cookie. So if we use authentication with HTTP only JWT cookie then we no need to implement custom logic like adding authorization header or storing token data, etc at our client application. Because once the user authenticated cookie will be automatically sent to the server by the browser on every API call. Authentication API: To implement JWT cookie authentication we need to set up an API. For that, I had created a mock authentication API(Using the NestJS Se

ReactJS(v18) Authentication With JWT AccessToken And Refresh Token

In this article, we are going to do ReactJS(v18) application authentication using the JWT Access Token and Refresh Token. JSON Web Token(JWT): JSON Web Token is a digitally signed and secured token for user validation. The JWT is constructed with 3 important parts: Header Payload Signature Create ReactJS Application: Let's create a ReactJS application to accomplish our demo. npx create-react-app name-of-your-app Configure React Bootstrap Library: Let's install the React Bootstrap library npm install react-bootstrap bootstrap Now add the bootstrap CSS reference in 'index.js'. src/index.js: import 'bootstrap/dist/css/bootstrap.min.css' Create A React Component 'Layout': Let's add a React component like 'Layout' in 'components/shared' folders(new folders). src/components/shared/Layout.js: import Navbar from "react-bootstrap/Navbar"; import { Container } from "react-bootstrap"; import Nav from "react-boot

A Small Guide On NestJS Queues

NestJS Application Queues helps to deal with application scaling and performance challenges. When To Use Queues?: API request that mostly involves in time taking operations like CPU bound operation, doing them synchronously which will result in thread blocking. So to avoid these issues, it is an appropriate way to make the CPU-bound operation separate background job.  In nestjs one of the best solutions for these kinds of tasks is to implement the Queues. For queueing mechanism in the nestjs application most recommended library is '@nestjs/bull'(Bull is nodejs queue library). The 'Bull' depends on Redis cache for data storage like a job. So in this queueing technique, we will create services like 'Producer' and 'Consumer'. The 'Producer' is used to push our jobs into the Redis stores. The consumer will read those jobs(eg: CPU Bound Operations) and process them. So by using this queues technique user requests processed very fastly because actually