Skip to content

Conversation

@cvc90
Copy link
Contributor

@cvc90 cvc90 commented Aug 19, 2025

Hi @jokob-sk,

Pull Request

Description

Changed the absolute path URL to relative path URL in report.php, this is a fix for issues with reverse proxy servers.

Changes

Update report.php (/front/report.php)

URLs were changed from absolute paths to relative paths

Test

Tested locally and works fine

Change static route to relative route in URL for proper proxy operation

Summary by CodeRabbit

  • Bug Fixes
    • Resolved an issue where notifications data failed to load or refresh in some deployments due to an incorrect absolute path. Switched to a relative request, improving compatibility across environments (subdirectory installs, reverse proxies) and reducing intermittent 404/cache issues. Users should now see notifications populate and refresh consistently. No user action is required.

Change static route to relative route in URL for proper proxy operation
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Aug 19, 2025

Walkthrough

Changed the fetch URL in front/report.php’s updateData from an absolute path (/php/...) to a relative path (php/...). No other logic or public/exported entities were modified.

Changes

Cohort / File(s) Summary
Frontend report fetch path
front/report.php
Switched fetch URL from absolute /php/server/query_json.php?file=table_notifications.json&nocache=${Date.now()} to relative php/server/query_json.php?file=table_notifications.json&nocache=${Date.now()}; all other code unchanged.

Sequence Diagram(s)

sequenceDiagram
  autonumber
  actor User as Browser
  participant ReportJS as front/report.php (client)
  participant Server as php/server/query_json.php

  Note over ReportJS: updateData()
  User->>ReportJS: Trigger update
  ReportJS->>Server: fetch("php/server/query_json.php?file=table_notifications.json&nocache=...")  <!-- relative path -->
  Server-->>ReportJS: JSON notifications
  ReportJS-->>User: Render updated table
Loading

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

I hopped from root to relative trails,
A tiny tweak that rides the gales.
No routes were harmed, no logic bent,
Just lighter footprints where I went.
Now carrots load without a fail—
nibble, fetch, and clear the trail! 🥕✨

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.

✨ Finishing Touches
  • 📝 Generate Docstrings
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Status, Documentation and Community

  • Visit our Status Page to check the current availability of CodeRabbit.
  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@cvc90 cvc90 marked this pull request as ready for review August 19, 2025 11:20
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (2)
front/report.php (2)

153-174: Keep both fetches consistent (cache-busting and URL construction)

There’s a second fetch to the same endpoint without the “nocache” param. For consistency and to avoid stale responses under some proxies/CDNs, consider adding cache-busting here as well and centralizing URL building (e.g., via a small helper that respects document.baseURI).

Example:

function notificationsUrl(params = {}) {
  const url = new URL('php/server/query_json.php', document.baseURI);
  url.searchParams.set('file', 'table_notifications.json');
  if (params.nocache !== false) url.searchParams.set('nocache', Date.now().toString());
  return url.toString();
}

// usage
fetch(notificationsUrl()); // with nocache
// ...
fetch(notificationsUrl({ nocache: false })); // if you explicitly want caching

90-126: Add response.ok check to fail fast on HTTP errors

Currently errors like 404/500 will flow into response.json() and throw less clear exceptions. A quick guard improves diagnosability:

.then(response => {
  if (!response.ok) throw new Error(`HTTP ${response.status} fetching notifications`);
  return response.json();
})
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

💡 Knowledge Base configuration:

  • MCP integration is disabled by default for public repositories
  • Jira integration is disabled by default for public repositories
  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 962bbaa and 086fa54.

📒 Files selected for processing (1)
  • front/report.php (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
  • GitHub Check: docker_dev
🔇 Additional comments (1)
front/report.php (1)

89-89: Relative fetch URL is valid

We confirmed that front/php/server/query_json.php exists and there is no <base href> in any header.php. Calling

fetch(`php/server/query_json.php?file=table_notifications.json&nocache=${Date.now()}`)

from /front/report.php correctly resolves to /front/php/server/query_json.php. No path change is required.

@jokob-sk jokob-sk merged commit bf2fae6 into netalertx:main Aug 19, 2025
4 checks passed
@jokob-sk
Copy link
Collaborator

Thanks @cvc90 !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants