I you fiddler core to monitor web traffic from the browser. However I have a problem when website does not exist. Fiddler then displays custom error message that website do not exist. I would like to display the standard error message from the browser... Maybe somebody knows how to do that?
Regards,
Andrzej
The short answer is that "You can't pretend like a proxy isn't there" when it really is. Having said that, the reason you see the Fiddler error message is because I deliberately pad the response body out to 512 bytes so that the error message is shown instead of IE's Friendly error message. If you'd instead like to show a different error message (including one shorter than 256 bytes to ensure that the client gets the browser's "Friendly" error page if that option is configured, you can do so by intercepting the FiddlerApplication.BeforeReturningError event and replacing the response body with whatever you'd like.
Related
Hi I don't understand why in my website the socket requests are multiple every time I send a message
using the browser console, on the network, the call comes out every time I send a message,
look at photos;
enter image description here
you can test the chat yourself, with every message you send the request appears on the network
Testing website
https://www.awesome-easley.37-187-54-25.plesk.page/
Can you tell me, if there is a way to not make the request list appear every time you send a message? do you have any suggestions?
using the site https://socket.io/demos/chat/, for example you send messages and no prompts appear using the console
enter image description here
why does the drop-down list appear on my site at each call and instead on the socket site no call is generated at each message sending? thank you
I thought it might be because of the cache, but I don't know where to start, does anyone have any suggestions?
I have an email address provided and managed by OVH (French ISP)
I'm trying to configure the account in Thunderbird (which I've been using with multiple accounts, including Gmail over IMAP, for years with great satisfaction). It's version 91.8.0 in Debian 11.3. No fancy tweaking or whatever.
I followed the instruction from my ISP (https://docs.ovh.com/fr/emails/configuration-email-configuration-pour-thunderbird/) - ok, it's a guide for the windows version, but that shouldn't be an issue.
The thing is, my address is like contact#somedomain.fr, but the mail server is ssl0.ovh.net.
I'm sure the password is correct, but when I go and validate the settings, Thunderbird tries to check the password, and it gets stuck there.
I noticed in the status bar that Thunderbird is actually trying to reach contact#somedomain.fr#ssl0.ovh.net... That must be (part of) the issue.
I tried to go to Advanced settings (so it creates the accounts and sends me to the account settings page), and there Thunderbird changes the actual server (which should be ssl0.ovh.net) to the email account's domain (somedomain.fr in my example)... Ain't that weird ? (also, it seems not to be able to determine the server type which remains empty, and most dropdown options, like authentication methods, are empty, or rather there are no labels).
Has anyone ever run into such an issue, and better yet, solved it ;-) ?
(not sure if the cross-domain tag is relevant)
Edit 2022-05-03 :
After many tests, still not working, but I have dug a little deeper.
I've set up the account manually with "Advanced configuration" so it doesn't try to check the password.
In the Folders panel, the account has no name and only a sub-folder named INBOX.
When I try to browse this INBOX folder, I get an error :
Unable to open the summary file for INBOX on contact#somedomain.fr. Perhaps there was an error on disk, or the full path is too long.
Running Thunderbird in full debug mode from CLI :
thunderbird --safe-mode --jsconsole --verbose
In the shell, from the verbose mode, I get this error repeatedly :
IPDL protocol error: Handler returned error code!
###!!! [Parent][DispatchAsyncMessage] Error: PClientManager::Msg_ForgetFutureClientSource Processing error: message was deserialized, but the handler returned false (indicating failure)
But I don't think this is related to my problem.
However in the JS console, I get an interesting message :
gloda.index_msg: Problem entering folder: INBOX, skipping. Error was: undefined:659: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.msgDatabase]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: resource:///modules/gloda/IndexMsg.jsm :: _indexerEnterFolder :: line 659" data: no]
Now, where do I go from here ?
I have a sign up custom policy and we get an intermittent "Bad Request" error after the submit button is clicked. I read somewhere that it could be that the request is too long but I am not sure if this is the same error. When page is refreshed it usually resolves and it goes to the redirect uri and processes successfully. Application insights logs don't have anything. How can I know what the specific cause?
console screen shot
There's an open issue here, where B2C doesn't handle an internal error properly if the page is left open for > ~4 hours. Does this match your scenario?
We have been getting an error prompt/alert in our XPages application at random times:
"An error occurred while updating some of the page...status:12152" and
"An error occurred while updating some of the page...status:12029"
We can't seem to pin it down to anything. Maybe someone has an idea of what these errors are referring to or maybe how to track it back to something? Thanks.
The HTTP 12152 error usually points to a network connection issue rather than anything specific to the browser or the Domino server.12029 again is down to an inability to make a connection to the server.
It sounds like the network connection is intermittent. I don't know what tools there are to test that, but I would suggest confirming you have a good, stable network connection between PC and server and that it's not getting negatively impacted by a firewall.
It looks like your application is trying to partially refresh content on the screen, and that this partial refresh fails. This can be because the component with that id is no longer found in the component tree.
Have a look at your XPages source code for controls with an id of MainContent and refreshPanel3 and find any partial refreshes on those controls. Check the rendered/loaded property for these controls to see if they are hidden in certain cases. If you do not render a control and want to display it using a partial refresh, you must partially refresh an outer component that contains the non-rendered control.
Use browser's network debug (F12 in Chrome/IE/Firefox w Firebug) to get real server response, it usually contains error page with more info. Failed partial refresh should be the last POST request.
My server returns a 403 forbidden error when a user tries to access a resource that they do not have access to. Along with the header the server also writes a small message describing the error.
In Firefox the error message gets displayed nicely and the user knows what's going on.
In Internet Explorer the message is hidden and replaced with the 403 Forbidden standard error page.
Are there any specific rules that allow me to display an error message across all browsers while still setting the status to 403 Forbidden?
Here is the RFC info on this status:
The server understood the request, but
is refusing to fulfill it.
Authorization will not help and the
request SHOULD NOT be repeated. If the
request method was not HEAD and the
server wishes to make public why the
request has not been fulfilled, it
SHOULD describe the reason for the
refusal in the entity. If the server
does not wish to make this information
available to the client, the status
code 404 (Not Found) can be used
instead.
It seems like I should be setting a message but IE just won't display it.
Try making your 403 page larger (i.e. more bytes). Some browsers assume that a short error page is the default page from the web server and decide to show their own, presumably more helpful text.
More info.
The implementation of error handling is browser dependent. In HTTP if you are just going to return a 403 error then you have to rely on the user agent (the technical name for the browser, the recipient of your error message may not be a browser) to handle out how it sees fit.
If you don't like how the browsers are handling 403 errors and want to ensure a consistent user experience across all browsers then redirect the user to your own 'permission denied' page. You can build a page that can explain to them why permission was denied and what they might be able to do about it. And it will be consistent for any browser.