I need to monitor a http request and response for web site running on remote web server. The web server makes lot of web service call and would like to trace them.
If the web site was running locally, Fiddler traces every web service call request and provides me with a report. Could someone please help me with how the same is possible
*e.g.
If the web application is running locally and calls two web services fiddler shows the total time on statistics. However, if the web application is running on web server hosted on different web server hosted internally (intranet) and I ran fiddler on my machine, I don't get the statistics for each web service call. All I can see is the total time for the aspx page.*
So question is how (if possible) can I trace the statistics of each web services invoked by web application that's running on different machine and fiddler is running on my machine.
Thanks.
You could always use WireShark http://www.wireshark.org/ to catch all the packets, if you are on the same network as the server, that is.
Say you're running a website on port 80 of a machine named WEBSERVER. You're connecting to the website using Internet Explorer Mobile Edition on a Windows SmartPhone device for which you cannot configure the web proxy. You want to capture the traffic from the phone and the server's response.
0.)Start Fiddler on the WEBSERVER machine, running on the default port of 8888.
1.)Click Tools | Fiddler Options, and ensure the "Allow remote clients to connect" checkbox is checked. Restart if needed.
2.)Choose Rules | Customize Rules.
3.)Inside the OnBeforeRequest handler, add a new line of code:
if (oSession.host.toLowerCase() == "webserver:8888") oSession.host = "webserver:80";
5.) navigate to http://webserver:8888
Requests from the SmartPhone will appear in Fiddler. The requests are forwarded from port 8888 to port 80 where the webserver is running. The responses are sent back through Fiddler to the SmartPhone, which has no idea that the content originally came from port 80.
You can setup Fiddler in your machine and set it as a proxy in the web application you want trace. Easy inside a network, not so easy accross the interwebs.
Related
I had a Web Server, which is configured with Ubuntu. Some web applications are hosted there and Clients from windows user browse/use those applications through the network. Application accessibility was smoother and faster and also was running without any interruptions.
But all the issues start when I configure the Windows Server and put all the users under a DOMAIN CONTROLLER. Now all the applications accessibility become too slow. Sometimes some pages are not loading at all.
I am mentioning all the IP configurations bellow-
Network Default Gateway: 172.16.0.1/16
Web Server- 172.16.2.2/16
Windows Server (Domain Controller)- 172.16.3.1/16
Using this Windows Server IP as DNS IP for all Client PC and also for the Web server.
Clients IP range: 172.16.1.1 to 172.16.10.254
Please See the Graphical view of my Configuration from the link below:
https://imgur.com/a/k3WLSg3
It was a DNS issue. I restored the Previous DNS settings in all clients and server then everything goes to normal condition.
Today I'm hosting a Laravel v4 web application on a MacMini. Why a Mac? Because I created the application logic in Objective-C (leveraging my experience with iOS dev). Whether or not this was the right choice isn't the point of the question.
What I'm interested in knowing is how can I separate my web and application server. For instance, if I put my web server on Linode (or whatever) how do I go about communicating back and forth between the web server and the application server? Is there some sort of resource I can look to to understand how to do this?
Assumptions
Here's some assumptions I'm making:
I'm guessing Laravel and the Objetive-C Application are part of the same "system" and so I'm just gonna treat this as if you need a web server to send requests to a PHP application.
The Linode server will be a web server which sends request to the PHP application (Laravel)
Hosting PHP Applications
There are three moving parts:
The web server (Apache, Nginx)
The application gateway (PHP-FPM)
The application
The gateway and the code must live on the same computer/server. The web server can live on a separate computer/server.
This means you'll need your Macintosh to run PHP-FPM, which can then listen for remote connects and send them to the PHP application.
Macintosh
Install php-fpm on your mac. Make sure it can listen for remote network connections. This is usually done in the www.conf file in the listen directory, you can listen for connections on the remote network interface (whatever IP address the computer is assigned).
Linode
Install Nginx or Apache and have it proxy FastCGI requests off to your macintosh server at the macintosh's IP address (the one you set up to listen to addresses in the step above).
Firewalls
You may need to ensure the firewalls at both ends allow incoming/outgoing connects on the networks being used to communicate to eachother.
I was trying to monitor request using TCP/IP Monitor.
But, I see there are two ports which are in use. One is the application port[8080] and other monitoring port[9833].
Can anybody tell , why there are two different ports?
When I launch the application it launches at 9833 instead of 8080. Why this change?
Eclipse monitoring is done by capturing all the requests sent to an application (a host and a port), dumping it on the Monitor console for you, then forwarding the original request to the application.
The monitored application itself will return its responses to eclipse (where it is the client from its prospective) where eclipse dumps it on the monitoring console too.
Now, how does eclipse captures the requests sent to the monitored application at the first place? it simply runs a service that accepts these requests (on behalf of the application) and forward it, this service also returns the application responses to the original requester.
Based on the above, in eclipse TCP/IP Monitor screen, the Local monitoring port is the port of the eclipse service (which you can use any available port number for), and the other Port is the monitored application port number.
So, in your case, the application you are monitoring is running on port 8080 and eclipse service is using the port 9833 (which is just a random port that you can change).
Your application port have not been changed, it still runs on 8080 and you can try that, but no data will be captured by eclipse TCP/IP monitor unless you use the port 9833.
Using XenApp6 on Windows 2008 R2 I have the windows Calculator as a test app. Apps are set to run on the server, and are not streamed to the client. When running Calculator from inside the network it runs as expected.
However, when accessing the app from an external web browser or Citrix Receiver, the client always times out and the Calculator app is not launched. I see incoming traffic on port 1494 (which is open) but there is no response from XenApp.
For both internal and external, I log in as Administrator and can see the citrix management console showing my test Calculator app.
Any ideas why it's timing out and not launching from the internet?
Thanks.
Chris
If the Citrix server's internal IP is being NATted to an external IP you may need to set an alternate address using altaddr on the Citrix server. Try this: Download the ICA file that the Citrix server passes when you launch a published app from a web browser, open it in a text editor, and see what FQDN or IP it is trying to connect to.
I asked a very similar question not too long ago and got some great responses. I've made it pretty far but still can't quite get things to talk. What I have is a PC running IIS and a web service inside of that. I'm trying to get the iPhone simulator on my Mac to be able to see this web service. I can ping my PCs local IP address from the Mac just fine, it's clearly alive and on the network. However, no matter what URL I enter into Safari the web service will not appear.
Any suggestions?
Thank you very much in advance.
Is this a web service or web application?
One fair possibility is that your Windows firewall could be blocking access to port 80. If it is, open your Windows firewall settings and add an exception for port 80 (Control Panel -> Windows Firewall -> Exceptions).
You might try using telnet on your Mac to test connecting to the web service/application.