Business
Jobs
  • About Us
  • Solutions
    • Job Postings
      Post your job and receive qualified candidates in 48h.
    • Candidate Assessments
      500+ technical and psychological tests, plus anti-fraud.
    • Headhunting
      Tailor-made executive search from start to finish.
    • Payroll + EOR
      Payroll dispersal and EOR across 15+ LATAM countries.
  • Pricing
  • Jobs

0

160
Views
Target URL accessibility and content availability checker

I'm working on a react application. In my application I have feature by which user can enter URL to refer something and save them for later use.

Some sample target url eg: Slack channel link for contact, SSO authenticated git hub repo link, google drive document link, box document link etc.

Now the scenario is that sometimes User entered URLs fail to load target url content, when I try to open the saved URLs later. Some possible cases:

  1. Document URL never existed
  2. Document URL was working at time of save but document removed later, so now not working

So, I want to implement Target URL checker functionality in my react web application something like chrome bookmark checker extension (https://chrome.google.com/webstore/detail/bookmarks-checker/eeckiajfclogcacnhgigljkcgabfcmco?hl=en) functionality, by which I can ensure that the Targeting URL is loadable in browser with 200 status or not and content availability in the document.

I tried to hit the target url by axios and checked the response status received in it but that approach was not working for Some cases like:

  1. Target url is an url of an sso authentic web application, in that case it return 302 due to redirection for sso authentication login page
  2. Targeted url is an url of application which using cookies for authentication, so always treating that as unauthorised even I have authenticated myself for the application in my browser in another tab
  3. Targeted url is an url of site, that redirecting to another url
  4. Getting CORS issue for all URLs

enter image description here

enter image description here

enter image description here

enter image description here

enter image description here

enter image description here

enter image description here

Please do suggest some approach. Thanks!

about 4 years ago · Juan Pablo Isaza
1 answers
Answer question

0

With a frontend-only solution such as you are building at the moment, I don't think you can solve the problem very well. You will stumble upon a number of challenges that might make the endeavour impossible, for example:

  • CORS rules not letting you access URLs at all.
  • Mixed content rules not allowing you to access non-encrypted URLs from a TLS-encrypted page.
  • Broken/self-sigend SSL certificates.

I would propose that you move the URL checks to a backend system that can freely open HTTP(s) connections without the restrictions of a browser.

about 4 years ago · Juan Pablo Isaza Report
Answer question
Find remote jobs

Discover the new way to find a job!

Top jobs
Top job categories
Business
Post vacancy Pricing Sales
Legal
Terms and conditions Privacy policy
© 2026 PeakU Inc. All Rights Reserved.
Andres GPT
Show me some job opportunities
There's an error!