Aquest lloc web fa servir cookies pròpies i de tercers per millorar l’experiència de navegació, i oferir continguts i serveis d’interès. En continuar la navegació entenem que acceptes la nostra política de cookies. Per a més informació consulta aquí.
Vés al contingut principal
Logo oficial de Metadecidim
  • Català Triar la llengua Elegir el idioma Choose language
    • Castellano
    • English
Registra't Entra
  • Inici
  • Processos
  • Assemblees
  • Iniciatives
  • Consultes
  • Jornades
  • Ajuda

Proposa noves funcionalitats

#DecidimRoadmap Dissenyant el Decidim entre totes

Fase 1 de 1
Obert 01-01-2019 - 31-12-2030
Veure les fases Envia una proposta
  • El procés
  • Debats
  • Proposa noves funcionalitats
  • Novetats
chevron-left Torna al llistat

Include a bit of additional details in the HTTP 500 error page message

Avatar: Antti Hukkanen Antti Hukkanen
14/01/2021 16:23  

**Is your feature request related to a problem? Please describe.**

When users will see the HTTP 500 page that states "There was a problem with our server", they generally just report this issue by copying the text on that page or by posting a screenshot.

Many times we can identify the correct error log entry by looking at the time of the report but sometimes it can be quite different than when the error actually happened.

This makes it sometimes hard to find the root cause of that particular user's problem.

**Describe the solution you'd like**

I'd like to add a bit of additional details to the HTTP 500 page. Not something that could potentially reveal sensitive information but at least something in order to map the correct log entry to the problem a bit easier.

I suggest adding the exact date+time stamp that appears in the logs to that page. On top of that, we could add a note stating: "Report this issue to the maintainers of this platform with the following details". Below that, we could add a box that includes some information to better identify the root cause.

This information could be:

  • Date+time of the exception as it appears in the log entry
  • User ID/nickname
  • The URL at the time of error
  • HTTP request method (GET/POST/etc.)

**Describe alternatives you've considered**

Looking at the time of the error report usually gives a slight hint when the error happened. But this information can be also lost in the email chains once it reaches the developers.

**Additional context**

Similar non-identifying information is typically included also in automated bug reports in the different operating systems. Some other software also implement such feature.

**Does this issue could impact on users private data?**

As the error report includes the user's ID or nickname, it reveals a bit of private data. However, typically they use the same email to report the issue anyways based on which you can also identify which user it was on the platform.

It should be also considered carefully what details to include with the additional report data. In case too much information is added, it has a potential impact on the private data. E.g. POST data should not be generally included since it could include some sensitive information e.g. during the OmniAuth callbacks.

**Funded by**

No funding available yet.

  • Resultats al filtrar per la categoria: Administració Administració

Llistat d'adhesions

Avatar: Virgile Deville Virgile Deville
Avatar: álvaro ortiz álvaro ortiz verified-badge
Número d'adhesions2
Include a bit of additional details in the HTTP 500 error page message Comentaris 1

Referència: MDC-PROP-2021-01-15923
Versió 1 (de 1) veure altres versions
Verifica l'empremta digital

Empremta digital

El text següent és una representació abreviada i hashejada d'aquest contingut. És útil per garantir que el contingut no hagi estat alterat, ja que una única modificació provocaria un valor totalment diferent.

Valor: 03b34acb6741a09f0e8f9f812b9baff4c8a6ac21e10f6145cfbf338f8c0362fe

Origen: {"body":{"en":"<p><strong>**Is your feature request related to a problem? Please describe.**</strong></p><p>When users will see the HTTP 500 page that states \"There was a problem with our server\", they generally just report this issue by copying the text on that page or by posting a screenshot.</p><p>Many times we can identify the correct error log entry by looking at the time of the report but sometimes it can be quite different than when the error actually happened.</p><p>This makes it sometimes hard to find the root cause of that particular user's problem.</p><p><strong>**Describe the solution you'd like**</strong></p><p>I'd like to add a bit of additional details to the HTTP 500 page. Not something that could potentially reveal sensitive information but at least something in order to map the correct log entry to the problem a bit easier.</p><p>I suggest adding the exact date+time stamp that appears in the logs to that page. On top of that, we could add a note stating: \"Report this issue to the maintainers of this platform with the following details\". Below that, we could add a box that includes some information to better identify the root cause.</p><p>This information could be:</p><ul><li>Date+time of the exception as it appears in the log entry</li><li>User ID/nickname</li><li>The URL at the time of error</li><li>HTTP request method (GET/POST/etc.)</li></ul><p><strong>**Describe alternatives you've considered**</strong></p><p>Looking at the time of the error report usually gives a slight hint when the error happened. But this information can be also lost in the email chains once it reaches the developers.</p><p><strong>**Additional context**</strong></p><p>Similar non-identifying information is typically included also in automated bug reports in the different operating systems. Some other software also implement such feature.</p><p><strong>**Does this issue could impact on users private data?**</strong></p><p>As the error report includes the user's ID or nickname, it reveals a bit of private data. However, typically they use the same email to report the issue anyways based on which you can also identify which user it was on the platform.</p><p>It should be also considered carefully what details to include with the additional report data. In case too much information is added, it has a potential impact on the private data. E.g. POST data should not be generally included since it could include some sensitive information e.g. during the OmniAuth callbacks.</p><p><strong>**Funded by**</strong></p><p>No funding available yet.</p>"},"title":{"en":"Include a bit of additional details in the HTTP 500 error page message"}}

Aquesta empremta digital es calcula mitjançant un algoritme de hash SHA256. Per reproduir-lo tu mateix, pots utilitzar una Calculadora MD5 en línia i copiar-hi les dades d'origen.

Compartir:

link-intact Compartir l'enllaç

Compartir l'enllaç:

Si us plau, enganxa aquest codi a la teva pàgina:

<script src="https://meta.decidim.org/processes/roadmap/f/122/proposals/15923/embed.js?locale=ca"></script>
<noscript><iframe src="https://meta.decidim.org/processes/roadmap/f/122/proposals/15923/embed.html?locale=ca" frameborder="0" scrolling="vertical"></iframe></noscript>

Reportar contingut inapropiat

Aquest contingut no és apropiat?

Motiu

1 comentari

Ordenar per:
  • Més antic
    • Més ben valorats
    • Recent
    • Més antic
    • Més discutit
Avatar: Andrés Andrés verified-badge
11/02/2021 10:23
  • Obtenir enllaç Obtenir enllaç

This would be awesome!!

Right now the troubleshooting involves going to an exception tracking system, like Errbit/Sentry/Rollbar and filtering by this controller/URL/user. Other times is easier to just say: "Can you do that again?" and do some tail -f or similar.

Other platforms what they do is give some kind of ID of the exception so the user can copy and send it, and then the administrators can look for this ID and the extra information.

Deixa el teu comentari

Inicia la sessió amb el teu compte o registra't per afegir el teu comentari.

Carregant els comentaris ...

  • Termes i condicions d'ús
  • Sobre la comunitat
  • Descarrega els fitxers de dades obertes
  • Metadecidim a Twitter Twitter
  • Metadecidim a Instagram Instagram
  • Metadecidim a YouTube YouTube
  • Metadecidim a GitHub GitHub
Amb llicència Creative Commons Web creada amb programari lliure.
Logo Decidim

Confirmar

D'acord Cancel·lar

Si us plau, inicia sessió

decidim Inicia sessió amb Decidim
O

Registra't

Has oblidat la teva contrasenya?