cleeclee123/pchecker

Proxy Checker API

pchecker's Issues

Error Handling in Both Verisons

Actually, handle errors properly instead of sending an empty object

• handling promise.all errors

Server Features

Add new Routes (Separating PChecker check method):

• Check Ping
• Check HTTPs (encryption)
• Check Proxy Server
  • Anonymity Check
  • Cause Analysis
• Get Location

PChecker object updates

• better error handling with Promise.all()
  • don't like "all or nothing"
• reference: https://stackoverflow.com/questions/30362733/handling-errors-in-promise-all
  • implement "Promise.when()" into PChecker
  • or just use Promise.allSettled()

Server KPIs Integration

Track specific proxy server metrics:

• uptime (calculated by us)
• average ping response (calculated by us)
• count (how many times that host:port has been checked with PChecker)
• more

Frontend Init

reference: https://www.loginradius.com/blog/engineering/guest-post/http-streaming-with-nodejs-and-fetch-api/

textbox to submit a bunch of IP addresses to validate them

implement this feature using HTTP Streaming

Make a quick proxy check object with user inputted parameters

parameters:

• desired level of anonymity
  • add support for specific header field exclusion
• desired encryption (HTTP vs HTTPs)
• performance?

Performance Stuff

https://sematext.com/blog/nodejs-memory-leaks/#:~:text=In%20simple%20terms%2C%20a%20Node,it%20runs%20out%20of%20memory.

memory stuff:

• test that destroy() actually works properly and removes all timeouts
• removing all listeners
• checkHTTPSSupport Lexical scoping/closures design
  • holds a reference to this.socket_ in the heap,
  • make sure that this.socket_ is freed properly

Performance stuff:

• checkHTTPSSupport() may run for the entire timeout, this is too slow
• find faster way to prove that proxy doesn't support HTTPS instead of just waiting for timeout