Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • A arachni
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 125
    • Issues 125
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 8
    • Merge requests 8
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Arachni - Web Application Security Scanner Framework
  • arachni
  • Issues
  • #533
Closed
Open
Issue created Dec 12, 2014 by Administrator@rootContributor

How to scan pages that always reply with HTTP 200

Created by: pirxthepilot

This is not really an issue, so forgive me if I posted in the wrong section.

I would like to know what is the best approach for web pages that replies with HTTP 200 no matter what you put in after it. Let's say we have a website with this page as the front page:

http://site/frontpage

If I visit any randomly-named URIs after it, e.g.

http://site/frontpage/random http://site/frontpage/cmd.exe

it always shows the front page with HTTP 200. It does not redirect with a 302; it keeps the URI.

As you can see, this is an issue with web app scans as the scanner will incorrectly detect that backdoors/common directories/backup directories/etc are present in the site.

Thanks for the help.

Assignee
Assign to
Time tracking