I capture errors in a catch block using captureException(error); in my NextJS app.
However in Sentry it doesnt show the entire error message as I would see in the developer console. For example it only says: AxiosError: Network Error (see image below).
How can I make sure I get the entire error object?
For example, in the developer console I see this:
Access to XMLHttpRequest at 'https://www.hello.com/' from origin 'http://localhost:3000' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.but this is not in sentry
What you are looking at on the screenshot is called a "breadcrumb". An event that happened during the user's session.
The Access to XMLHttpRequest... is a browser network error, and it's not exposed to the JS API, so you won't be able to capture it.
If you want to investigate what's available for your network errors, you can use beforeBreadcrumb callback, as detailed in https://docs.sentry.io/platforms/javascript/enriching-events/breadcrumbs/#customize-breadcrumbs
Related
I get this error in the console when i try to
#import url('https://fonts.google.com/specimen/Space+Grotesk');
in my CSS file. after a little research i found that it's a security setting in Microsoft edge but I couldn't find a way to solve it
I don't want to change my tracking settings and adding the URL to exceptions didn't work.
i tried to turn track prevention off and i got another error message
Cross-Origin Read Blocking (CORB) blocked cross-origin response https://fonts.google.com/specimen/Space+Grotesk with MIME type text/html. See https://www.chromestatus.com/feature/5629709824032768 for more details.
I'm trying to fetch data from a website (https://gesetze.berlin.de/bsbe/search). Using Mozilla, I've taken a look at the network analysis. Usually, I'm just messing around with the parameters of the POST-Request to see how I might influence the response of the server. But when I simply re-send the request (making no changes at all), I'm getting HTTP-response 500. The server answer states as message: security_notAuthenticated.
Can anyone explain that behaviour? The request is done by the same PC, the same browser in the same session, and there is no login function on that website. Pictures shown below.
Picture 1 - Code 200
Picture 2 - Code 500
The response security_notAuthenticated indicates, that your way of repeating the request omits some authentication-related information.
When I repeat the request, using Mozilla Firefox's "Resend" or "Edit and resend" function, the Cookie header is not sent with the request. Although it occurs in the editable header list when using "Edit and resend" it's missing when watching the actual sent request. I'm not sure whether this is a feature or a bug.
When using Firefox's "Use as Fetch in Console" function, the header will automatically be included and you still have the ability to change the headers and the body. The fetch API is a web standard and some introductory material about fetch can be found on MDN.
If you want to do custom requests, in the browser, fetch is a good option.
In other environments and languages you usually use some HTTP client (just search the web for "...your language... http request" or similar, you will find something).
I have an angular that sends calls to Apigee. After tracing the calls i can see that a response is returned. However the client does not get the response. I have no idea what i could be missing in this instance.
I have set up CORS correctly on Apigee and can see the options preflight response getting called successfully. The issue really is on the second call, a response is returned but the client receives null data
Well, working with the description you've sent, what you could do:
Debug the API call using the Chrome Developer tools: use ctrl-shift-J and then choose the 'network' tab. See if the clal is coming in. Clicking on the specific API call shows you the response
also maybe check the console that is shown when using above command (crl-shift-J)
indeed check the Apigee trace. But if the trace shows a reply is sent, then probably it is.
add some console.log in the Angular application or try to debug it so that you are certain it's an Angular issue.
maybe share some code so that we can better help you.
While attempting to implement Google+ sign in, I receive this error:
Upon clicking the sign in button, I receive a redirect_uri_mismatch, error stating that:
The JavaScript origin in the request:
http://70132bd6.ngrok.com did not match a registered JavaScript origin.
I have added the link (along with several others just in case) in my developer console under origins:
How do I resolve this mismatch issue?
Additionally, why is there a prepended storagerelay:// in the redirect uri of the request details. It says it is: redirect_uri=storagerelay://http/70132bd6.ngrok.com?id=auth109348. Where is the extra part coming from?
Please make sure you are using correct client_id. It is common that developers created multiple clients, and set those origins on a different client. Please double check.
When I open the details window on any of my API Proxies using the APIGee Developer Dashboard, I get two error messages
Error while fetching object: No server entry found with ID long token goes here
and
Server Error: No server entry found with ID same long token goes here
The page still seems to function partially, but this prevents me from seeing my API proxy deployments and proxy information, or from tracing calls to the API.
I can't figure out what triggered this error - I don't see any recent config changes and the API proxy and the endpoint services are up and running. There's no reference to 'Server Entry' anywhere on the config page or in the help, which makes it hard to know where to start when fixing this.
Please see here: http://status.apigee.com/
This could be related to the platform release in flight.
You can subscribe to this for future updates too.
If the issue still persists, do raise a support ticket http://apigee.com/about/support/request-support