Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

headless mod doesn't work properly with SPA (Single Page Application) #502

Open
lebik opened this issue Jun 28, 2023 · 1 comment
Open
Labels
Type: Bug Inconsistencies or issues which will cause an issue or problem for users or implementors. Type: Question A query or seeking clarification on parts of the spec. Probably doesn't need the attention of all.

Comments

@lebik
Copy link

lebik commented Jun 28, 2023

It seems like katana doesn't work properly with SPA (Single Page Application) like AngularJS

katana version:

v1.0.2

Current Behavior:

Results (number of URLs) without headless mode and with headless mode are the same

Expected Behavior:

Results (number of URLs) in headless mode should contain more URLs compared to running without headless mode

Steps To Reproduce:

Experiment #1 - crawling SPA without headless mode

katana -d 6 -jc -timeout 40 -f url -H headers.txt -aff -ef 'css,gif,png' -u 'http://testspa.local'

Experiment #2 - crawling SPA in headless mode

# login and save session
/usr/bin/chromium --user-data-dir=/home/kali/testspa

# run katana in headless mode
katana -d 6 -jc -timeout 40 -f url -H headers.txt -aff -ef 'css,gif,png' -u 'http://testspa.local' -hl -noi -scp /usr/bin/chromium -cdd /home/kali/testspa 

Anything else:

In my example, I need to login first before I can start crawling, so without headless mode I pass the cookie file (-H headers.txt), while in headless mode I am logging in manually and then passing the -cdd option

@lebik lebik added the Type: Bug Inconsistencies or issues which will cause an issue or problem for users or implementors. label Jun 28, 2023
@Mzack9999 Mzack9999 added the Type: Question A query or seeking clarification on parts of the spec. Probably doesn't need the attention of all. label Dec 28, 2023
@Mzack9999
Copy link
Member

Related #579

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Bug Inconsistencies or issues which will cause an issue or problem for users or implementors. Type: Question A query or seeking clarification on parts of the spec. Probably doesn't need the attention of all.
Projects
None yet
Development

No branches or pull requests

2 participants