Skip to content

Navigation Menu

Explore
By company size
By use case
By industry
View all solutions
Topics
- AI
- DevOps
- Security
- Software Development
- View all
Explore
- GitHub Sponsors
  Fund open source developers
- The ReadME Project
  GitHub community articles
Repositories
- Enterprise platform
  AI-powered developer platform
Available add-ons
Pricing

Search code, repositories, users, issues, pull requests...

Search

Clear

Search syntax tips

Provide feedback

We read every piece of feedback, and take your input very seriously.

Include my email address so I can be contacted

Saved searches

Use saved searches to filter your results more quickly

Name

Query

To see all available qualifiers, see our documentation.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

Dismiss alert

roots / acorn Public

Notifications You must be signed in to change notification settings
Fork 96
Star 836

Code
Issues 13
Pull requests 4
Actions
Projects
Security
Insights

Additional navigation options

Code
Issues
Pull requests
Actions
Projects
Security
Insights

🚑 Fix responses always returning `200` on WordPress routes (Fixes #411)#412

Merged

Log1x merged 4 commits intomainroots/acorn:mainfrom fix/411roots/acorn:fix/411Copy head branch name to clipboard

Nov 6, 2024

+10-9

Conversation Commits4 (4)Checks Files changed

Commits

Commits on Nov 6, 2024

🚑 Fix responses always returning 200 on WordPress routes (Fixes #411 )
Log1x
committed
🔧 Add back middleware config
Log1x
committed
🔧 Add back API middleware config
Log1x
committed
🔧 Set the response status code to the current value of http_response_code()
Log1x
committed

Footer

© 2025 GitHub, Inc.

Footer navigation

Terms
Privacy
Security
Status
Docs
Contact

You can’t perform that action at this time.