preetkaran20

## IPv6 Tests
http://[::ffff:169.254.169.254]
http://[0:0:0:0:0:ffff:169.254.169.254]

## AWS 
# Amazon Web Services (No Header Required)
# from http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-metadata.html#instancedata-data-categories
http://169.254.169.254/latest/meta-data/iam/security-credentials/dummy
http://169.254.169.254/latest/user-data
http://169.254.169.254/latest/user-data/iam/security-credentials/[ROLE NAME]

preetkaran20

[
  {
    "name": "OWASP VulnerableApp",
    "url": "https://github.com/SasanLabs/VulnerableApp"
  },
  {
    "name": "OWASP VulnerableApp-facade",
    "url": "https://github.com/SasanLabs/VulnerableApp-facade"
  },
  {

preetkaran20

Squashing Git Commits

The easy and flexible way

This method avoids merge conflicts if you have periodically pulled master into your branch. It also gives you the opportunity to squash into more than 1 commit, or to re-arrange your code into completely different commits (e.g. if you ended up working on three different features but the commits were not consecutive).

Note: You cannot use this method if you intend to open a pull request to merge your feature branch. This method requires committing directly to master.

Switch to the master branch and make sure you are up to date:

preetkaran20

<fileupload version="1">
    <staticlocation>
        <uriregex>asdadad</uriregex>
    </staticlocation>
    <dynamiclocation>
        <uriregex/>
        <startidentifier/>
        <endidentifier/>
    </dynamiclocation>
    <parseresponse>