Web Bot-Detection Header Capture
Budget: $10 – $30 USD
I need a lightweight, server-side mechanism that automatically records five specific values from every incoming HTTP request on my web application:
• User-Agent
• _uds cookie
• udi-fingerprint cookie
• Sec-Ch-Ua-Platform header
• Referer header (والـ Referer)
The sole purpose is security and fraud detection, with a particular focus on spotting automated traffic and other bot activity. Because this runs on a web platform only, I want the code to drop straight into my existing stack without altering user-facing behaviour or slowing response times.
Deliverables
1. A well-structured middleware or script (Node.js, PHP, Python, or Go—your choice) that captures the fields above on every request.
2. Secure storage logic (database table or log file) with timestamps and the visitor’s IP.
3. A short README that explains installation, configuration, and how I can query the captured data to flag suspected bots.
4. A brief test or demo page proving the capture works.
Acceptance criteria
• All five values are reliably stored on each request.
• No personally identifiable information is logged beyond the items listed.
• The solution can be enabled or disabled via a single config flag.
• Implementation passes a simple load test of 500 requests/second without noticeable latency.
If you have experience building security logging tools or bot-detection pipelines, this should be a quick, focused task.
• User-Agent
• _uds cookie
• udi-fingerprint cookie
• Sec-Ch-Ua-Platform header
• Referer header (والـ Referer)
The sole purpose is security and fraud detection, with a particular focus on spotting automated traffic and other bot activity. Because this runs on a web platform only, I want the code to drop straight into my existing stack without altering user-facing behaviour or slowing response times.
Deliverables
1. A well-structured middleware or script (Node.js, PHP, Python, or Go—your choice) that captures the fields above on every request.
2. Secure storage logic (database table or log file) with timestamps and the visitor’s IP.
3. A short README that explains installation, configuration, and how I can query the captured data to flag suspected bots.
4. A brief test or demo page proving the capture works.
Acceptance criteria
• All five values are reliably stored on each request.
• No personally identifiable information is logged beyond the items listed.
• The solution can be enabled or disabled via a single config flag.
• Implementation passes a simple load test of 500 requests/second without noticeable latency.
If you have experience building security logging tools or bot-detection pipelines, this should be a quick, focused task.