Jump to content
WAPT Forum
Sign in to follow this  
Guest deepak

Not able to view Body and Browser View in Logs

Recommended Posts

Guest deepak

I am not able to view Body and Browser view in Logs.

Are these not available in Trial Version?

 

Regards,

Deepak

Share this post


Link to post
Share on other sites
Guest oidsman

Deepak,

 

I was using the rial version and the browser view in the log does work. When using it you need to make sure you are clicked onto one of the 'HTTP/1.1 200 OK messages in the top pane (HTTP Protocol Summary). There should be an entry (amongst others) for the actual page etc.

 

Regards,

Share this post


Link to post
Share on other sites
Guest angela
I am not able to view Body and Browser view in Logs.

Are these not available in Trial Version?

 

Regards,

Deepak

 

Hi Deepak,

 

Just in case: the trial version is fully functional, except the number of virtual users available (it is limited to 20).

 

Share this post


Link to post
Share on other sites
Guest Ezequiel
Hi Deepak,

 

Just in case: the trial version is fully functional, except the number of virtual users available (it is limited to 20).

 

I'm experiencing the same problem:

 

I am not able to see, for example, a .css file on the "Body" nor "Browser view" I can't see a .jpg file either.

but I'm able to see an .emp file without a problem...

 

I see the GET requests and I see the HTTP/1.1 200 OK response from the Web Server (IIS6)

but I can't see the actual files ....

I don't even know if this is a normal behavior or not...

any comments?

Share this post


Link to post
Share on other sites
I'm experiencing the same problem:

 

I am not able to see, for example, a .css file on the "Body" nor "Browser view" I can't see a .jpg file either.

but I'm able to see an .emp file without a problem...

 

I see the GET requests and I see the HTTP/1.1 200 OK response from the Web Server (IIS6)

but I can't see the actual files ....

I don't even know if this is a normal behavior or not...

any comments?

 

Yes, It's a normal behavior. WAPT stores in a log HTML sources only.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×