apache / apache/answer

Getting HTTP 302 -> /403 on displaying uploaded images after answer "update"

Open
#722 13 comments 0 reactions 0 assignees View on GitHub
bug
Dominant language
Go
Stars
15.7k
Forks
1.4k
Avg merge
3d 8h
Merged PRs (30d)
7

Description

## Describe the bug

Not sure when it started (maybe with 1.2.1 or after running 1.2.1 for some days, but not sure), and have no idea how to analyze the following issue:

Uploading images works well, they're written to the `updates` folder in the file system.
But when displaying them, answer returns a HTTP 302 redirecting to `/403`.

Uploaded avatars and the brand image are still working.

There are no additional information in debug log, pardon me, I've no idea how to taggle this.

The installation is private, when changing it to public, images are shown. so it seems to be related to login session handling for images downloads.

### To Reproduce

Steps to reproduce the behavior:

1. having a private answer
1. deploy a rebuild answer binary (`answer build --with-plugins...`)
1. uploaded images result int http 302 -> /403 ![image](https://github.com/apache/incubator-answer/assets/40993644/09adc3e4-b87b-404e-96c1-875544851699)
1. clear cookie `visit` and reload page
1. uploaded images work again

### Expected behavior

Uploaded images continue to being shown also after answer updates

### Screenshots

If applicable, add screenshots or video to help explain your problem.

### Platform

- Device: Any
- OS: Official answer container image
- Version: v1.2.1 `--with-plugins`

Contributor guide

No contributing guide indexed for this repository

Research direction

No source file or test is named. Reproduce the issue on a private installation by rebuilding the Answer binary, then inspect the image download path and login-session handling; done means uploaded images remain accessible after an update without clearing the visit cookie.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
authentication, backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.