请求授权有问题 [英] Problem with request authorisation

问题描述

嗨！最近，随着AngularJS从1.5.8升级到1.7.5，我们进行了一些安全升级.我们在应用程序中使用Loopback 3.0.到目前为止，我们遇到了一个问题，即具有正确访问令牌的请求不会通过授权.这样的 服务器重启后，该问题将随机出现，并且woudl消失.有趣的是，问题出现后，应用程序将停止记录到应用程序日志文件.然后，再次修改日志(例如，关闭 然后再次进行应用程序日志记录)-这样服务器就不会重新启动，而只是更改日志记录方案-然后问题似乎就消失了.

Hi! Recently we have made some security upgrades along with upgrade of AngularJS from 1.5.8 to 1.7.5. We are using Loopback 3.0 in our app. So far we have run into the issue, where requests with proper access token would not pass the authorisation. Such issue would appear randomly and woudl disappear after the server restart. Interesting part is that after the issue appears, the application stops logging to application log files. And then again, after we make some changes for the logs (for example turn off and on again the application logging) - so that the server does not restart and just changes the logging scheme - the problem seems to dissappear then.

我的问题是:打开/关闭日志需要什么流程?我们不确定问题从何而来，而我们最新的结论是否围绕着神秘的原木行为而聚集.我们不怀疑日志是造成问题的原因， 但是了解日志记录机制背后发生的情况将为我们的问题提供一些启示.您有任何想法吗?

My question is: what processes stand behind turning on/off the logs? We are not sure where from comes the issue and our state of the art conclusions gather around the mysterious logs behaviour. We do not suspect, that the logs are the reason of our problem, but understanding what happens behind the logging mechanism would put some light onto our problem. Do you have any idea?

推荐答案

您是否正在使用文件系统或Blob应用程序日志?请注意，文件系统应用程序日志每12小时关闭一次，以免耗尽应用程序的所有存储空间.

Are you using the file system or blob application logs? Please note that file system application logs turn off every 12 hours to avoid using up all of your app storage space.

这篇关于请求授权有问题的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！