framework/views/error/csrf_token_mismatch.blade.php

@extends('flarum.forum::layouts.basic')

@section('content')
  <p>
    {{ $message }}
  </p>
  <p>
    <a href="javascript:history.back()">
      {{ $translator->trans('core.views.error.csrf_token_mismatch_return_link') }}
    </a>
  </p>
@endsection
Merge pull request from GHSA-3wjh-93gr-chh6 * Integration tests: Memoize request handler as well This is useful to send HTTP requests (or their PSR-7 equivalents) through the entire application's middleware stack (instead of talking to specific controllers, which should be considered implementation detail). * Add tests for CSRF token check * Integration tests: Configure vendor path Now that this is possible, make the easy change... * Implement middleware for CSRF token verification This fixes a rather large oversight in Flarum's codebase, which was that we had no explicit CSRF protection using the traditional token approach. The JS frontend was actually sending these tokens, but the backend did not require them. * Accept CSRF token in request body as well * Refactor tests to shorten HTTP requests Multiple tests now provide JSON request bodies, and others copy cookies from previous responses, so let's provide convenient helpers for these. * Fixed issue with tmp/storage/views not existing, this caused tmpname to notice. Fixed csrf test that assumed an access token allows application access, which is actually api token. Improved return type hinting in the StartSession middleware * Using a different setting key now, so that it won't break tests whenever you re-run them once smtp is set. Fixed, badly, the test to create users etc caused by the prepareDatabase flushing all settings by default. * added custom view, now needs translation 2019-06-24 09:14:39 +02:00			`@extends('flarum.forum::layouts.basic')`

			`@section('content')`
			`<p>`
			`{{ $message }}`
			`</p>`
			`<p>`
removed link to home, go back, which is always the case with csrf token invalidation 2019-06-24 10:49:31 +02:00			`<a href="javascript:history.back()">`
Determine error view and message based on type ...not based on status code. To simplify this logic, we now use the same error "type" both when routes are not found and specific models are not found. One exception is ours, one is from Laravel, but for the purposes of error handling they should be treated the same. Fixes flarum/core#1641. 2019-08-14 19:43:36 +02:00			`{{ $translator->trans('core.views.error.csrf_token_mismatch_return_link') }}`
Merge pull request from GHSA-3wjh-93gr-chh6 * Integration tests: Memoize request handler as well This is useful to send HTTP requests (or their PSR-7 equivalents) through the entire application's middleware stack (instead of talking to specific controllers, which should be considered implementation detail). * Add tests for CSRF token check * Integration tests: Configure vendor path Now that this is possible, make the easy change... * Implement middleware for CSRF token verification This fixes a rather large oversight in Flarum's codebase, which was that we had no explicit CSRF protection using the traditional token approach. The JS frontend was actually sending these tokens, but the backend did not require them. * Accept CSRF token in request body as well * Refactor tests to shorten HTTP requests Multiple tests now provide JSON request bodies, and others copy cookies from previous responses, so let's provide convenient helpers for these. * Fixed issue with tmp/storage/views not existing, this caused tmpname to notice. Fixed csrf test that assumed an access token allows application access, which is actually api token. Improved return type hinting in the StartSession middleware * Using a different setting key now, so that it won't break tests whenever you re-run them once smtp is set. Fixed, badly, the test to create users etc caused by the prepareDatabase flushing all settings by default. * added custom view, now needs translation 2019-06-24 09:14:39 +02:00			`</a>`
			`</p>`
			`@endsection`