Problem/Motivation

With the internal link, such as below, we receive a fatal error.
Client error: `GET https://drupal-org.ddev.site/admin/structure/block` resulted in a `403 Forbidden`

Steps to reproduce

Use an internal link for the service. Look at my example.

Proposed resolution

Adding an error handler.

Remaining tasks

None.

User interface changes

None.

API changes

None.

Data model changes

None.

CommentFileSizeAuthor
Screenshot from 2025-12-02 10-20-22.png184.37 KBjust-me

Issue fork opengraph_filter-3560986

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

just-me created an issue. See original summary.

just-me’s picture

just-me commented
Assigned: Unassigned » just-me

just-me opened merge request !8

just-me’s picture

just-me commented
Assigned: just-me » Unassigned

Hi,

I've added an error handler. Now users will see a warning instead of a fatal error.

loon’s picture

loon commented
Status: Needs review » Needs work
just-me’s picture

just-me commented

Hi,

as was discussed:
- You can use internal links and not see the warning.
- The result of the response, this case bad response, was cached as well as a successful one.
- An error will be shown in the reports menu.
- Added a null check to the line, which was the cause of an error.

just-me’s picture

just-me commented
Status: Needs work » Needs review
just-me’s picture

just-me commented

Hi,

The link below will take you to an issue that relates to the "Failed preview" task.
https://www.drupal.org/project/opengraph_filter/issues/3561625

  • loon committed 4c79da0b on 8.x-1.x authored by just-me 
    Issue #3560986: Added an error handler
loon’s picture

loon commented
Status: Needs review » Fixed

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.