4 commits

Author	SHA1	Message	Date
Hannah Wolfe	4f5fb3d820	Swapped common for @tryghost/errors in core/server/web ... - Update all references to common.errors to use @tryghost/errors - Use dereferencing to only require used bits of common in each file	2020-04-09 19:40:00 +01:00
Hannah Wolfe	0107ac848a	✨ Improved x-request-id handling ... - Currently, we create a request ID for internal use if one isn't set & this is used in logs - If a custom request ID is set via X-Request-ID header, this gets logged, however, we don't return this with the response - Means that a custom ID gets lost on the way back out, and makes tracing requests through a system trickier - This change ensures that if X-Request-ID is set on the request, it is also set on the response so that requests can be properly traced - It's easy to set this in e.g. nginx so that the feature becomes available - Ghost doens't need to do this - Note: also split request id handling out into new middleware	2019-09-22 18:23:45 +01:00
Christoph Tavan	834a5a0521	Replaced v1 for v4 uuids (#10871) ... * Swapped v1 with v4 UUID as requestId when logging no issue v1 UUID are based on current time and the hardware MAC address of the machine where they are being generated. As such they have much more complex semantics than v4 UUIDs which are simply randomly generated. Unless there's a specific requirement for the special semantics of v1 UUIDs it is simpler and less error prone to simply go for v4 UUIDs whenever just a unique identifier is needed. * Swapped v1 with v4 UUID when creating a temporary contentFolder no issue v1 UUID are based on current time and the hardware MAC address of the machine where they are being generated. As such they have much more complex semantics than v4 UUIDs which are simply randomly generated. Unless there's a specific requirement for the special semantics of v1 UUIDs it is simpler and less error prone to simply go for v4 UUIDs whenever just a unique identifier is needed. * Swapped v1 with v4 UUID when creating a temporary exportFolder no issue v1 UUID are based on current time and the hardware MAC address of the machine where they are being generated. As such they have much more complex semantics than v4 UUIDs which are simply randomly generated. Unless there's a specific requirement for the special semantics of v1 UUIDs it is simpler and less error prone to simply go for v4 UUIDs whenever just a unique identifier is needed.	2019-07-15 14:01:02 +08:00
Rishabh Garg	fcd275f6c0	Refactored web/middleware and web/utils to web/shared (#9892) ... refs #9866 - Moved web/middleware to web/shared/middlewares - Moved util file to web/shared/utils	2018-09-20 20:04:34 +02:00

Renamed from core/server/web/middleware/log-request.js (Browse further)