Testing for HTTP Incoming requests (OTG-INPVAL-017) - Revision history

Tony Hsu HsiangChih: /* Port Forwarding */

2016-04-09T23:55:46Z

‎Port Forwarding

2016-04-09T23:37:58Z

‎TCP-level Network Traffic Capture

2016-04-09T23:37:39Z

‎Reverse Proxy

2016-04-09T23:37:07Z

‎Reverse Proxy

2016-04-09T23:36:53Z

‎Reverse Proxy

2016-04-09T23:34:57Z

‎TCP-level Network Traffic Capture

2016-04-09T23:33:12Z

‎TCP-level Network Traffic Capture

2016-04-09T23:31:56Z

‎TCP-level Network Traffic Capture

2016-04-09T23:29:35Z

‎References

2016-04-09T23:28:00Z

‎Tools

← Older revision		Revision as of 23:55, 9 April 2016
Line 36:		Line 36:

	=== Port Forwarding ===		=== Port Forwarding ===
		+	Port forwarding is another way to allow us intercept http requests without changes of client side.
		+	You can also use Charles as a SOCKS proxy to act as port forwarding or uses of Port Forwarding tools.
		+	It will allow us to forward all coming client side captured traffic to web server port.

		+
		+	The testing flow will be:
		+	<pre>
		+	1. Install the Charles or port forwarding on another machine or web Server
		+	2. Configure the Charles as Socks proxy as port forwarding.
		+
		+	</pre>

	=== TCP-level Network Traffic Capture ===		=== TCP-level Network Traffic Capture ===

@@ Line 43: / Line 43: @@
 The testing steps will be:
+<pre>
 . Activate TCPDump or WireShark on Web Server side to capture network traffic
@@ Line 51: / Line 51: @@
 . Reply the http requests
 Fiddler or Charles are recommended since these tools can capture http traffic and also easily edit/reply the modified http requests.

@@ Line 22: / Line 22: @@
 The testing steps:
+<pre>
 . Install Fiddler or Charles on Web Server
@@ Line 32: / Line 32: @@
 . Modify Http requests and replay the modified requests for testing
 === Port Forwarding ===

@@ Line 24: / Line 24: @@
 . Install Fiddler or Charles on Web Server
 . Configure the Fiddler or Charles as Reverse Proxy
 . Capture the http traffic
 . Inspect Http traffic
 . Modify Http requests and replay the modified requests for testing

← Older revision		Revision as of 23:36, 9 April 2016
Line 20:		Line 20:

	For Linux platform, Charles Web Debugging Proxy may be used.		For Linux platform, Charles Web Debugging Proxy may be used.
		+
		+	The testing steps:
		+
		+	1. Install Fiddler or Charles on Web Server
		+	2. Configure the Fiddler or Charles as Reverse Proxy
		+	3. Capture the http traffic
		+	4. Inspect Http traffic
		+	5. Modify Http requests and replay the modified requests for testing

	=== Port Forwarding ===		=== Port Forwarding ===

← Older revision		Revision as of 23:34, 9 April 2016
Line 39:		Line 39:

	Fiddler or Charles are recommended since these tools can capture http traffic and also easily edit/reply the modified http requests.		Fiddler or Charles are recommended since these tools can capture http traffic and also easily edit/reply the modified http requests.
		+	In addition, if the web traffic is HTTPS, the wireshark will need to import the web server private key to inspect the HTTPS message body. Otherwise, the HTTPS message body of the captured traffic will all be encrypted.

	== Tools ==		== Tools ==

@@ Line 31: / Line 31: @@
 . Activate TCPDump or WireShark on Web Server side to capture network traffic
 . Monitor the captured files (PCAP)
 . Edit PCAP files by Ostinato tool based on need
 . Reply the http requests
 == Tools ==

@@ Line 26: / Line 26: @@
 === TCP-level Network Traffic Capture ===
 This technique monitor all the network traffic at TCP-level.
-TCPDump or WireShark tools can be used. However, these tools don't allow us edit the captured traffic and send modified http requests for testing.
+TCPDump or WireShark tools can be used. However, these tools don't allow us edit the captured traffic and send modified http requests for testing. To replay the captured traffic (PCAP) packets, Ostinato can be used.
 == Tools ==

@@ Line 37: / Line 37: @@
 * pcapteller
 * replayproxy
 == References ==