URI::http::Dump 0.03

URI::http::Dump is a Perl module to assist in the reverse engineering of URL parameters.

SYNOPSIS

## Whatever you get the picture.
use constant URI
=> 'http://longassuri:obsecureport'
. '/stupid_path/segments/probably/not/needed/but/there/for/fun/'
. 'dumbFile.that.says.nothing.of.security'
. '?Stupidquerry=HexencodedNonsense&Oth=er&cra=p'
;

use URI::http::Dump;
URI::http::Dump->new( URI )->makeLifeEasy;

perl -MURI::http::Dump -e'URI::http::Dump->new("uri")->makeLifeEasy';

## Same as.
perl -MURI::http::Dump -e'mle("http://google.com")'

## Overview of process
$ perl -MURI::http::Dump -e'mle("http://google.com")'
$ vim url.txt ## change stuff
$ perl -MURI::http::Dump -e'mle("http://google.com")'
http://google.com/foobar.do?a=b

$ firefox $( perl -MURI::http::Dump -e'mle("http://google.com")' ) && vim url.txt

The simplicity of Unix is in the way it treats (most) everything like a file, and this is just a simplicity mechanism so you can treat URIs as a file too via YAML markup, ie, easily manipulate them with a text editor.

Say you're trying to reverse engineer a website for the purpose of automation and the URL that is causing annoyance has a shit ton of parameters with numerous different quirks: ie, base64 encoding, custom encoding, hexecoding nonsense, or maybe they just spelt everything in pig latin. Now, for reasons known to the reader, you need to make sense of this: this module will help you.

This module really has a small scope, and the route of action it takes depends entirely on the existance of the URI's file-store. On the first invocation, before the file-store exists, URI::http::Dump will decompile the URL provided to new() to its basic URI components and store it to a file.

On the second invocation, URI::http::Dump will compile the URI from the components in the file-store and output the URI to stdout. It will continue on this route for each subsequent invocation until the file-store is deleted. Then it will re-render the file from the arguments to constructor so you can begin the process again.

Because of the internal function of the URI module query segments encoded and unencoded in the respective steps, ie., the file will probably look more ledgable than the URI by default.

If you have deep voodoo you need to do to the URI in an automated fashion you can utilize a Moose around method modifier on the ->load or ->dump functions.

Product's homepage

Requirements:

· Perl