How to turn on (back) Fiddler to show HTTP protocol errors? - fiddler

Few hours ago I turned off showing HTTP protocol errors by checking the checkbox (Do not show) in the modal error dialog. Now I am do not find where to turn on.
I must be missing something, but I've reviewed all the Options dialog tabs, still not found...

If you navigate to Tools -> Fiddler Options -> General, change the value in If protocol violations are observed to something other than Do nothing.

Related

manifest.json display property has invalid option of browser

The documentation seems to state that there are four options for the "display" property within a manifest.json: fullscreen, standalone, minimal-ui and browser
I decided upon 'browser' for one of my apps, but the message from Chrome (Version 76) says "Manifest 'display' property must be one of 'standalone', 'fullscreen' or 'minimal-ui'". The message also appears if I leave 'display' undefined.
Is 'browser' an obsolete option or has it just not made it into the latest Chrome version yet?
(I probably should mention that the message appears in Chrome DevTools>application>manifest).
Valid options for display are fullscreen, standalone, minimal-ui and browser according to https://developer.mozilla.org/en-US/docs/Web/Manifest/display.
In order to show the Add to Home Screen Prompt, display must be set to must be one of: fullscreen, standalone, or minimal-ui, see https://developers.google.com/web/fundamentals/app-install-banners/
browser display option is like leaving the field empty.
When you use standalone it looks like native app. When you use fullscreen there is no status bar etc. Probably you want to use standalone, because fullscreen has very specific use-case (e.g. gaming).
I finally got around to reporting it as a bug.
https://bugs.chromium.org/p/chromium/issues/detail?id=1330323
The immediate response was...
The behaviour is seen from M-85.This is is a non regression issue
hence marking it as untriaged and requesting some one from dev team to
look into the issue.

Why WebIde shows error for alert and console.log?

I am using WebIde of SAPUI5 development.
If I write a console.log or alert it shows error of unexpected Alert and so on inside of the editor.
While the code works and I prefer to not see these errors inside of the editor.
How can I customize WebIde to not show these kind of errors.
While it is discouraged to use console.log and alert statements in your code because
[...] such messages are considered to be for debugging purposes and therefore not suitable to ship to the client [...]
http://eslint.org/docs/rules/no-console
and
[...] JavaScripts’ alert, confirm, and prompt functions are widely considered to be obtrusive as UI elements and should be replaced by a more appropriate custom UI implementation [...]
http://eslint.org/docs/rules/no-alert
you can have your Linter configured to bypass these checks (although I would not recommend to do so)
But keep in mind these checks are not specific to SAPUI5 or Web IDE, rather for every Javascript project!
Anyway, since Web IDE uses ESLint, to disable the check, add the following on top of the affected Javascript file:
/*eslint-disable no-console, no-alert */

fiddler autoresponder not working

I added a rule (flash file), specified the new flash file I want fiddler to respond with (use instead of the browser one). I've cleared my browser cache, and every time I play the stream, the browser flash file is captured again (instead of auto-responding) with the one saved already!!!
It used to work just fine, but now it appears as if the auto-responder (although checked) is not working at all...it's just a pass-through!!!
As explained in the forum post where you asked the same question
There are three possibilities:
1> The AutoResponder itself is disabled (checkbox at the top)
2> The AutoResponder rule is disabled (checkbox at the left of the rule)
3> The rule you've written doesn't match the target request's URL.
Sharing a screenshot of Fiddler might help me tell you which problem you're encountering.
On the top of the list EricLaw gave in the previous answer, I add a new one:
You need to ensure your Fidler has the "Capturing Traffic" mode enabled. Either press F12 or go to "File" -> "Capture Traffic" and make sure you have a "Capturing.." icon on your left bottom corner.
I had a similar issue, and I solved it by enabling decryption of HTTPS traffic.
You can do this by going to Tools > Options > , then check Decrypt HTTPS Traffic
I had the same problem. I drag-dropped from the left, "main", window into the autoresponder so the "request matches..." column auto-populated. As a sanity check I unchecked "unmatched requests passthrough" to ensure that the match rule was indeed picking it up. If it hadn't nothing would appear in the main window at all. But it did appear so the rule was matching.
The issue with Fiddler is in the "then respond with..." column. Right-click for "Edit Response...", edit the response in the popup window of tabs, press Save, close the box.
When you retry your URL, your edited response isn't returned. Fiddler returns the original response. Even if you Edit Response again, it'll show what you typed in, but it never actually returns it.
To fix, you have to save the intended response to a file on your hard drive and edit it there.

Eclipse RCP StatusManager - how to change the title

I am trying to use StatusManager to display and/or log messages. Not necessarily bad and nasty problems, but also info's or warnings. This is what I basically do:
Status status= new Status(IStatus.INFO, MainPlugin.ID, "Some info message");
StatusManager.getManager().handle(status, StatusManager.SHOW | StatusManager.LOG);
Works well, but I can't find the way to modify the default title of the popup dialog - it always says "Problem Occurred". Going through the maze of eclipse code brought me here to ask this question because I am totally lost... Any ideas?
Unfortunately setting dialog title is not possible now. The dialog is generated based on IStatus object when you give a proper flag (such as StatusManager.SHOW), but the interface does not define a title. To allow what you want, the IStatus interface should be extended.
The same problem occurs in Eclipse 4 (there is a new StatusReporter class).
You can follow the bug Bug 386023 which postulates exactly what you want (on Eclipse 4 platform).

QTP - See through invisible window (JBoss error mask upon returning to page from a popup)

Steps:
QTP identifies a few links on a web App.
I click on this link (using qtp).
Application opens a popup to change a few values.
I submit the Image button after changing the values.
I return back to the original page, which is open in the background (never closed).
But QTP now does not recognize those few links (as said in point 1), instead it only shows a hierarchy upto Page as shown below:
Browser("name:=JBoss Web/2.1.7 - Error report").Page("title:=JBoss Web/2.1.7 - Error report")
I have to use a Browser("name:=JBoss Web/2.1.7 - Error report").refresh code to get the properties visible again everytime I get back from the popup.
Notes - This occurs on a few machines (different behavior on different machines). Very few systems do not show the JBoss error when accessing through QTP. OS, QTP and browser versions are same with default settings.
Upon changing registry value as shown below, I was able to access all of the web elements most of the times. However, at times, I get the JBOSS error (browser,page) mask again which seems to be impenetrable.
[HKEY_CURRENT_USER\Software\Mercury Interactive\QuickTest Professional\MicTest\Packages\StdPackage\Settings]
"SkipWndMovedOut"=dword:00000001
Any suggestions on what needs to be done to access all the elements every time - by surpassing the JBOSS error mask page every time?
Thanks,
Anuroop.
What version of QTP are you using?
This sounds like a known bug which was fixed for QTP10 by hotfix QTPWEB_00065 (there are hotfixes for other versions too).
I suggest you contact HP support in order to get the relevant hotfix.
As a workaround in the meantime you can use Browser's undocumented RefreshWebSupport method which reconnects QTP to the page without refreshing the page.