You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the smp.publicurl has been misconfigured (e.g. missing protocol 'http://') the server name is not set at start up.
If the application is in this state it will take the host header of the first call to set the serverName.
In our case it was a bot scanning our application that was using an x-rated domain as there host header.
When this happens you'll see the following message in the log:
"Static server information set: [StaticServerInfo@0x345f634f: scheme=http; serverName=..."
This serverName is used for a number of forwards and generation of links which resulted is some strange behavior of the application.
The text was updated successfully, but these errors were encountered:
When the smp.publicurl has been misconfigured (e.g. missing protocol 'http://') the server name is not set at start up.
If the application is in this state it will take the host header of the first call to set the serverName.
In our case it was a bot scanning our application that was using an x-rated domain as there host header.
When this happens you'll see the following message in the log:
"Static server information set: [StaticServerInfo@0x345f634f: scheme=http; serverName=..."
This serverName is used for a number of forwards and generation of links which resulted is some strange behavior of the application.
The text was updated successfully, but these errors were encountered: