Make WordPress Core

Opened 4 years ago

Closed 4 years ago

#35836 closed defect (bug) (invalid)

Security update caused errors in connections using proxy and firewall

Reported by: gabrielavelar Owned by:
Milestone: Priority: normal
Severity: normal Version: 4.4.2
Component: General Keywords:
Focuses: administration, multisite Cc:
PR Number:


We use a proxy and a firewall.
We use Wordpress as our commercial site
In the specific case the administrative area of ​​the site , after the security update, the wp- admim is not displayed correctly . This occurs on any computer " locked" by the firewall and the error is only in the Wordpress admin pages.

It has run several tests , and there is no lock on the site or on the proxy and firewall. It seems that Wordpress is failing to load the css correctly these connections.

Remembering , there are no errors on theme , there is no error in the log , no locks on the connection.
Bug occurred after the automatic security update.

Nós utilizamos um proxy e um firewall.
Utilizamos o Wordpress como nosso site comercial
Na caso específico a área administrativa do site, apos a atualização de segurança, o wp-admim não é exibido corretamente. isto ocorre em qualquer computador "bloqueado" pelo firewall e o erro é somente nas páginas de administração do Wordpress.

Foi executado vários testes, e não há nenhum bloqueio no site ou no proxy e firewall. Parece que o Wordpress não está conseguindo carregar o css corretamente nestas conexões.

Lembrando, não há erros no tema, não há erro no login, não há bloqueios na conexão.
Bug ocorreu apos a atualização automática de segurança.

Change History (4)

#1 @dd32
4 years ago

  • Milestone Awaiting Review deleted
  • Resolution set to invalid
  • Status changed from new to closed

Hi @gabrielavelar

Unfortunately without any information as to what your proxy is blocking, there's nothing we can do to fix it. It's likely your proxy security software needs updating with newer rules.

I'm marking this as invalid for now, as it's not clear that it's a bug in WordPress itself.

#2 @gabrielavelar
4 years ago

The error occurred after the security update for Wordpress , the new version coast error solutions with redirects . I believe the Wordpress platform failed to link the CSS files in protected connections for prozy server and a firewall.
The site works normal, but after entering the Admin area ( wp- admin ) or any page editing , CSS files are not loaded , they are not found.
Proxy servers and firewall have no problems , are current and are especially tailored to our company , I checked with the technical department and we made several tests . The error caused after the update does not understand that behind the connection there is a prozy .
Remembering . The site is on the white list , there is no locks. Everything up and running normally.
I'm going back to old version of Wordpress .

O erro ocorreu apos a atualização de segurança do Wordpress, na nova versão costa soluções de erros com redirecionamentos. Acredito que a plataforma Wordpress não conseguiu fazer a ligação dos arquivos CSS em conexões protegidas por um servidor prozy e um firewall.

O site funciona normal, porém apos entrar na área de Admin, (wp-admi) ou qualquer pagina de edição, os arquivos CSS não são carregados, não são encontrados.

Os servidores proxy e firewall não possuem problemas, estão atualizados e são customizados especialmente para nossa empresa, verifiquei com a área técnica e efetuamos vários testes. O erro causado apos a atualização não compreende que atras da conexão existe um prozy.

Lembrando. O site está na lista branca, não existe bloqueios. Tudo atualizado e funcionando normalmente.
Vou voltar para versão antiga do Wordpress.

#3 @gabrielavelar
4 years ago

  • Resolution invalid deleted
  • Status changed from closed to reopened

#4 @johnbillion
4 years ago

  • Resolution set to invalid
  • Status changed from reopened to closed

Please ask your technical department to continue their investigation into the problem. Without any information about your proxy, your firewall, or your internal infrastructure, there's nothing WordPress can do about this issue, which is almost certainly a configuration problem with your particular infrastructure.

In addition, if you take a look at the changes between 4.4.1 and 4.4.2 you'll see that there were no changes to the way that scripts or styles are loaded, nor indeed were there any between 4.4.0 and 4.4.2.

Note: See TracTickets for help on using tickets.