"This Request needs a higher Gitea Version" or "Gitea version > 1.7 required" #519
Labels
No Label
⌚ Major-release
⌚ Minor-release
⚔️ Wontfix
⚙️ CI
⛏️ Breaking
✨ Duplicate
❌ Invalid
❓ Question
❤️ Support
➡️ Frontport
➡️ Needs-frontport
🔙 Backport
💭 Brainstorming
🐛 Bug
🔭 Cannot-reproduce
🧺 Cleanup
🧾 Confirmed
💬 Discussion
📄 Documentation
🎯 Enhancement
🩹 External-dependecy
📱 F-droid
🎉 Feature
👋 Good-first-issue
🤾 Google-play
🔙 Has-backport
🚀 Improvement
🚨 Investigate
🌠 Long-term
🔙 Needs-backport
🧺 Needs-cleanup
📡 Needs-feedback
📈 Performance
📌 Priority-critical
📌 Priority-high
📍 Priority-low
📍 Priority-medium
🥑 Ready
🪒 Refactor
🔙 Regression
📸 Release
🔒 Security
💡 Suggestion
🧪 Testing
🌐 Translation
💻 UI/UX
🪜 Upstream
🟦 Website
🙇♂️ Needs-help
🛰️ API-dependency
🛡️ Blocked
🏗️ Build
🗒️ Changelog
🗄️ Repository
🗓️ Summary
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: gitnex/GitNex#519
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Created By: @Renfle
# What do you want to address?
(This step is required; examples are shown below)
# Describe your matter briefly
When opening some specific types of files, the error messages appear: "This reguest needs higher gitea version than installed. Please upgrade your instance to the latest version" or "Gitea version greater 1.7 required" "
What did you expect? (Useful when addressing bugs
(This step is optional)
Some additional details (Useful, when we are trying to reproduce a bug)
(This step is optional; an example is shown below)
We would appreciate some screenshots or stacktrace's, but this is also not required.
(Screenshots and stacktrace's can go here)
Thank you for your time.
Hi @Renfle, it maybe related to #517. But can you tell us which type of files throw this error?
Created By: @Renfle
ok, i did a little more research
in the root directory of the repositories everything works. any file can be opened
gut as soon as I go down one level, the error messages appear.
Garten/common.yaml > works as expected
Garten/common/common.yaml > error message
partdb/startup.php > works
partdb/inc/authors.php > error message
espeasy/platformio.ini > works
espeasy/tools/build_ESPeasy.sh > error message
everthing works via web interface and git (no ssh, only https)
Created By: @Renfle
its the same bug, any file type, only in subfolders
maybe interesting
apache 2.4.48 (Debian) reverse proxy
apache include.conf
Created By: @Renfle
I noticed something about my reading of the Apache log files.
this is a working request
this fails
That's interesting. The problem is coming from
%2F
.Can you add this
AllowEncodedSlashes On
in httpd.conf and try.Created By: @Renfle
I have just changed the relevant include file
/var/www/XXXXXX/conf/include.conf
Now the error message is gone and the file opens.
luckily I still allow TLSv1.2, otherwise it would have been interesting.
just a quick question.
why do you use the normal slash and the encoded variant in the url?
Great. 👍
It shuould work with TLSv1.3 too. You can try and let us know if you have problems with it.
In the mean time I will close this issue.