Search the site’s resources

A single starting point to find the method, source or situation relevant to your question.

Find a method for your task

All words must match, regardless of case or accents. Search stays in the selected language.

From two characters: use arrows to choose, Enter to open, Escape to close. You can also submit the full search.

1682 results

Clear filters

Guide
Resource Timing: three sizes and several possible causes of zero
Encoded body size, decoded body size and the transfer indicator describe different objects. These rules come from the W3C Candidate Recommendation Draft of 1 September 2026, still undergoing standardization.
Guide
Navigation Timing: choose the right finishing boundary
Navigation time is meaningful only with its start and end events. This reference follows the W3C Working Draft of 1 September 2026; the diagram shows logical order rather than measured durations.
Guide
Measure duration without mixing clocks
A date locates an event; a monotonic clock measures an interval. The High Resolution Time Working Draft of 1 September 2026 distinguishes these uses and execution contexts’ own origins.
Guide
Server-Timing: read what the server actually declares
The W3C Working Draft of 7 April 2026 lets a server expose named metrics. Its non-normative example below contains seven entries, including durations, descriptions and deliberately absent fields.
Guide
Base64: check alphabet, padding and unused bits
Base64 represents bytes using ASCII characters. It is neither encryption nor a digest: decoding recovers the data. The seven RFC 4648 vectors below are public references with no real secret.
Guide
HMAC: what a shared key changes
An unkeyed digest and a keyed authentication code provide different information. Two RFC 4231 cases make the distinction verifiable with explicit test bytes.
Guide
HTTP digests: received content and representation can differ
Content-Digest and Repr-Digest cover different scopes. Three published exchanges from RFC 9530 Appendix B show why correct digests can differ without a change to the complete document.
Guide
Canonical JSON: a precise contract beyond sorted keys
JCS, described in Informational RFC 8785, defines a deterministic representation for cryptographic operations. It is stricter than arbitrary JSON and more complete than removing spaces.
Guide
UTF-8 BOM: an invisible marker is still bytes
An invisible character can affect a digest and a first field. Before editing a file, separate binary preservation, decoding and the receiving format’s rules.
Guide
BagIt: verify a file collection beyond a ZIP archive
BagIt 1.0, described by Informational RFC 8493, organizes payloads, metadata and manifests. It separates file presence from checksum verification without certifying document truth.
Guide
Link a legal unit to its establishments
Before matching French records, choose the required level. An establishment record and its legal-unit record can both be correct while showing different addresses or activities.
Guide
Person, organisation and publication: three identities
A bibliographic record links several objects. Check each relationship in the consulted material rather than transferring an identifier’s credibility to the entire result.
Guide
Read GeoJSON coordinate order
Inspect the actual input format before copying coordinates. Do not automatically swap a pair because another tool displays its fields in a different order.
Guide
Distinguish a dataset, distribution and service
When two links appear to describe the same data, compare their objects before counting two sources. Organise collection so each value can be traced to the representation actually consulted.
Guide
Read an archive at record level
A page replay helps reading; archive metadata identifies the examined resource. Retain both levels when a conclusion depends on an earlier state.
Guide
Parse an ECLI before citing a decision
The official identifier ECLI:EU:C:1998:27 provides a real structural example. Retrieve the decision and its text rather than inferring its meaning from the identifier.
Guide
Count patent publications or families
Before counting, state what constitutes a row and which rule groups documents. A comparison loses meaning when it silently mixes publications and families.
Guide
What robots.txt actually describes
Separate a published rule from the response actually received by a crawler. For an important path, retain the consulted file and the URL check.
Guide
A real satellite image with two dates to retain
This observation distinguishes acquisition from publication of its record. Treat the image as an identified document, then consider the metadata needed before taking measurements.
Guide
Google: distinguish crawlers and results
A crawl record should identify the resource and agent. Use documented names to read logs, then inspect results in the search surface being studied.
Guide
Bing: separate three crawler roles
Identify a request’s function before interpreting server logs. A preview request and a search crawl answer different questions.
Guide
DuckDuckGo: separate search and assisted answers
When studying a citation, record the feature observed rather than treating all requests as one activity. The two documented crawlers serve different uses.
Guide
Brave: a distinctive crawling control
The crawler documentation describes behaviour relevant to interpreting requests. Do not look only for a string containing the service name before deciding it is absent from your logs.
Guide
HTTP cache: separate storage, freshness and validation
A stored response is not necessarily reusable immediately. RFC 9111 separates freshness lifetime, response age and validation requirements. These are transport rules, not evidence that a page’s statements remain accurate.

Choose a starting point

Choose a method

Start from a task: verify, compare, document or decide.

Check a source

Examine the origin, date, scope and limits of information.

Understand a term

Find definitions before applying a protocol.

How can I refine the search?

Start with the topic: Enter one or two specific terms: citation, CSV or provenance. Every word must be present, so a long sentence can exclude useful pages.
Broaden before filtering: Search all families first. Then select a guide, protocol or source according to the kind of answer you need.
Try different wording: Try a synonym or a term in the selected language. Quotes, OR and asterisks are not search operators.

DEEPER READING / PRACTICE

Turn internal search into a useful user journey

A query produces several close results. Reading should help to distinguish the need definition folder, detailed method and implementation tool.

Updated on 2026-10-21.

Priority checks

Formulate a specific need and then try neighboring terms. Read the descriptions and select the type of resource according to the searched step: understand, run or control.

Interpretation pitfalls

The first result is not always the best document to the context. An absence can come from the vocabulary used rather than a lack of content.

Working record to retain

A short route connects a need definition page, a guide and a checklist. Maintaining unresolved questions helps to rebuild research.

PRACTICAL CASE / WORKED EXAMPLE

A natural requirement does not match the exact title

The following case illustrates an approach to defining the need. Situations are pedagogical: they serve to examine the choices and conditions of success, without describing a fulfilled mission or announcing a guaranteed result.

Example context

A reader is looking for how to check a number, while the resources use the word indicator. The results must allow to continue despite a different formulation of the title.

Suggested approach

Try the neighboring terms and read the descriptions. Differentiate methods of calculation, comparison and verification of sources. Choose the resource that corresponds to the actually sought-by-step.

Conclusion and next step

Research becomes a path of solution. The questions still open serve to clarify the next query instead of multiplying the words without clear intention.

Questions for deeper practice

How do you improve a search without losing the initial need?

Keep the starting question and then specify the object, operation and resource type. Useful results give a complementary vocabulary, but their title should not automatically replace the reader's target.

DETAILED WORKSHOP / APPLICATION

Refine a query for the task to carry out

01 / Prepare the necessary information
Describe the initial question and the desired result. Identify the object, operation and type of resource that could help: file, method or tool.
02 / Carry out the approach
Try a formulation and read the descriptions. Release the useful terms and test the variants without giving up the intention. Compare the resources found according to their contribution to the route.
03 / Examine an alternative situation
If the results are close but too general, specify the operation or scope. A well-classed page is not necessarily the one that meets the searched step.
04 / Decide on the next step
Research is useful when it leads to a resource whose response can be identified. Open questions are used to prepare for the next consultation.
05 / Hand over the verification records
Keep a short track with request, resource and supplement. The reader can restart his work without repaired the tests that have led to useful content.

ANNOTATED WORKING DOCUMENT / REVIEW GRID

A track record from a request

The note retains question, tried formulations, useful results and next resource. It distinguishes the exploration vocabulary from the initial goal of the reader.

On a small screen, scroll the grid horizontally to read all three columns.

Example situations to assess
Observation	Supported interpretation	Next step
A resource responds to the desired operation.	The result can serve as a useful step in the course.	Keep the passage and choose the necessary supplement.
The results remain general despite the good topic.	The request must specify action, object or scope.	Try an appropriate formulation without losing the initial question.
The first result has the word but not the answer.	The presence of the term does not prove its relevance.	Read the descriptions and compare the contribution of resources.

Reviewing the working document

The final verification verifies that each step reduces an open question. A link list is not yet a useful path if the reader cannot explain what each page brings.

REPORTING / EXAMPLE WORDING

Presentation of results: Turn internal search into a useful user journey

Point to clarify

A search result must be judged according to its contribution to the searched operation.

Before handing over

Check that the track keeps the initial question despite the vocabulary variants.

Example of a qualified conclusion

The resource selected meets the described stage of the need. The questions still open guidelines the next consultation and remain distinct from the answer found.