Closed Sicks3c closed 3 years ago
Hi, @Sicks3c. Sometimes, it happened because the dependencies can't parse response from URL. Try to download first then run wadl-dumper. Workaround:
wget http://url/file.wadl
, then run dumperwadl-dumper -i file.wadl
Hi @dwisiswant0
Thank you for fast reply When I use the file method I only get the paths not the full url
Instead of
Regards
Hi @dwisiswant0
Thank you for fast reply When I use the file method I only get the paths not the full url
Instead of
Regards
Yea that because you don't use -b
flag to print with base URL prefix. But it all depends on the source origin WADL file, some add the base URL directly or just an endpoint. For example if the 2nd URL (like your image) you download - and execute it like your first proof, the result will be same as your second proof (CMIIW).
Feel free to reopen this issue if you have more questions. 🙂
Describe the bug
This bugs occurs when the target has insecure SSL
To Reproduce
Expected behavior
Output all the possible paths in the wadl directory
Screenshots
Environment (please complete the following information):
Additional context Add any other context about the problem here. Full output log is probably a helpful thing to add here.