Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[GOWS] - Link preview request sends User-Agent and Accept values swapped

Open Beginner friendly
#2,322 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 2 days

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
83/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
go

Research direction

The report points to src/media/links.go in the GOWS code at lines 44–45. Read that header construction and check which values are assigned to User-Agent and Accept; reproduce with a link sent through the sendText endpoint if needed. Done when the request uses a browser-style value for User-Agent and text/html for Accept, preventing the reported swap.

Written by the indexing model from the issue text.

Description

bug
Describe the bug

When GOWS generates a link preview, the HTTP request it makes to the target URL has the User-Agent and Accept header values swapped

Version
{
  "version": "2026.8.2",
  "engine": "GOWS",
  "tier": "PLUS"
}

Steps

To Reproduce Steps to reproduce the behavior:

  1. Send any link message with sendText endpoint:
  2. View the link from whatsapp application
Expected behavior

The link preview should be able to read all browser information from most server

Requests - Responses

Some link preview return with
403 - Forbidden

Additional context

There is a mismatch value located in this file:
https://github.com/devlikeapro/gows-plus/blob/master/src/media/links.go
Line 44-45

Expected
User-Agent: Mozila ....
Accept: text/html ....

Dominant language
TypeScript
Stars
7.6k
Forks
1.8k
Avg merge
2d 21h
Merged PRs (30d)
7

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from devlikeapro/waha

All issues in devlikeapro/waha

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.