I'm using HttpModule v1.0.2 in a web form application in .NET 4.
I would like to log the decrypted assertion for debugging purpose, how can I do it?
The SpOptions.Logger log only the EncryptedAssertion.
No, as far as I can remember, there is no logging point after decrypting the assertions, nor any notification/callback that can be used for logging.
It's on my list of ideas for the next version, but that will only be available for .NET 6.
Related
I'm using google-cloud-cpp SDK from here: https://github.com/googleapis/google-cloud-cpp. However, I can't seem to figure out how to enable logging for the client library and find out where the log file goes. I'm interested in seeing all the HTTP requests being made to the endpoint. Appreciate any help and/or examples.
You need to set two environment variables:
GOOGLE_CLOUD_CPP_ENABLE_CLOG=yes will redirect the logs to std::clog, the library does not create a log backend otherwise.
GOOGLE_CLOUD_CPP_STORAGE_TRACING=http,raw-client otherwise logging is not even turned on.
You can find more information about environment variables for the SDK in the API Notes section of: https://googleapis.dev/cpp/google-cloud-storage/latest/index.html
This is a weird situation, NLog users usually contact when NLog does not send emails but I am contacting you because NLog is sending emails.
I configured NLog using UseNLog(). I have nlog.config file. Thats it. Nothing else is set to configure it.
Nlog.config file just have target set to email me.
I do not even inject Logger in any OData controller.
It is a Asp.net Core project.
I am manually throwing exception from one of my controller. And it sends me email.
I am not even calling Logger.LogError().
How is this happening?
NLog integrates with ASP.NET Core logging. That isn't only a logger abstraction, but also ASP.NET Core is writing logs to that abstraction (debug info, http calls, errors etc).
So if ASP.NET Core catches an exception, it will write to the logging abstraction and NLog is configured to process the logging with UseNLog and the nlog.config.
This will be probably more clear if you set-up the internal log of NLog, it shows the internals.
See also the getting started with NLog and ASP.NET Core 2, in the example below you will see some output examples.
i've created a wcf service library with ado .net entity framework to handle the retrieving of data from the database and send it to the user.
i've been testing it in visual studio without any problems.
so, i moved the dll of the service and the xml configuration file to the bin folder of weborb, changed the web.config to add my service.
but when i invoke the service from the webconsole i get this error:
>The server was unable to process the request due to an internal
>error. For more information about the error, either turn on
>IncludeExceptionDetailInFaults (either from ServiceBehaviorAttribute
>or from the <serviceDebug> configuration behavior) on the server in
>order to send the exception information back to the client, or turn on
>tracing as per the Microsoft .NET Framework 3.0 SDK documentation and
>inspect the server trace logs"
can anyone give any help with this?
how can i get a working wcf service library using ado .net entity framework in weborb?
help would be appreciated.
thanks in advance.
Have you checked the WebORB log?
Then start off by trying the WebORB examples from here.
The WebORB log should give you more detail about the error. With that info, I would post a question on the WebORB forum.
I have an mvc2 project built for .NET 3.5. I have a library that I wrote in 4.0 that I need for the 3.5 project, so I changed the target framework and now the anywhere the anti-forgery token it throws:
Validation of viewstate MAC failed. If this application is hosted by a
Web Farm or cluster, ensure that configuration specifies
the same validationKey and validation algorithm. AutoGenerate cannot
be used in a cluster.
I found this question but no luck with any of the suggestions. I created a static machine key in my config but it doesn't help. Anybody have any idea what could be the problem. I don't understand why it worked fine before.
You have to close all browser windows to continue.
The AntiForgeryToken cookie is a session-cookie, and is encrypted / decrypted using the machine key. If the machine key changes (or is set to auto-generate), then rendering the AntiForgeryToken will fail.
Restarting your browser windows will clear the cookie, and MVC will create a new, valid cookie next time.
When I deploy newer version of my GWT application, I get sometimes this log error:
SEVERE: GwtRpcEventSrvc: WARNING: Failed to get the SerializationPolicy 'www.host.com:22041/MYAPP/'; a legacy, 1.3.3 compatible, serialization policy will be
a result.
Question 1) Is it a problem of serialization policy files remaining
in browser cache?
Question 2) How to prevent such log message? I tried to add changing
URL request param to nocache.js (<script
src="MyApp.nocache.js?v=123"...) but it did not help.
Try clearing your browser cache. It worked for me.. after searching a lot of a lot of ways to solve it.
See:
how to clear cache in gwt?
Stop browser scripts caching in GWT App
GWT Caching Concept
In summary: you need to set HTTP headers not to cache the .nocache.js files via your web server or a servlet filter