-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Odd refresh behaviour when Proxied. #73
Comments
Can you paste in the terminal output for TiddlyServer?
…On Fri, Sep 13, 2019 at 5:22 PM Mystikite ***@***.***> wrote:
Hi, I am running 2.1.3, w/ default config.
However, i have apache2 w/ a virtual server pushing ProxyPass and
ReverseProxyPass to http://localhost:8080/mywiki.
If i make changes via the TiddlyServer :8080/mywiki address, and refresh
the page, things appear as expected.
if i make changes via the proxied virtual domain, then reload my page, the
changes do not appear to have been written.
before moving to TiddlyServer, i ran this wiki successfully as a node.js
server proxied, so i know that the proxy itself is not preventing put/get,
etc.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#73?email_source=notifications&email_token=AADLMQDI3XC35UW3OGBRDD3QJQAATA5CNFSM4IWUFD22YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HLKRQTA>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AADLMQEUPUCY6NZAP7Q52HDQJQAATANCNFSM4IWUFD2Q>
.
|
I can, but i think i've wasted your time. I'm guessing that I either have to go back to multiple nodeJS, or try my luck w/ the multiuser patches i've seen floated about. |
Your use-case is the main direction I am trying to improve in TiddlyServer,
so I am actually very interested in all the information you can provide.
…On Sat, Sep 14, 2019 at 1:33 AM Mystikite ***@***.***> wrote:
I can, but i think i've wasted your time.
after much testing, the issue happens when multiple people are viewing the
site. if i ensure noone else is viewing the wiki, and only have a single
connection to it, it behaves as expected whether proxied or not. only when
multiple connections are made to the wiki, and changes made in one session,
that the other session becomes unstable.
I'm guessing that I either have to go back to multiple nodeJS, or try my
luck w/ the multiuser patches i've seen floated about.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#73?email_source=notifications&email_token=AADLMQEY2NEGOFKNVNWWY7LQJRZSVA5CNFSM4IWUFD22YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6WU3PI#issuecomment-531451325>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AADLMQGSQVMBZGCQJVMNNM3QJRZSVANCNFSM4IWUFD2Q>
.
|
ok. i will pull some log data, interspersed w/ directory info, and upload sometime tomorrow |
Sorry for teh delay, I had unexpected family visits derail things. == Browser 1: Initial load, create and save 'new tiddler' === == Browser 2: Initial load, create and save 'new tiddler 1' === == Browser 1: delete 'new tiddler' === == Browser 1: shift+reload === == Browser 2: shift+reload === === Browser 2: open + delete 'new tiddler 2' === Browser 2: repeated attempts to open then delete new tiddler 1 === |
Hi, I am running 2.1.3, w/ default config.
However, i have apache2 w/ a virtual server pushing ProxyPass and ReverseProxyPass to http://localhost:8080/mywiki.
If i make changes via the TiddlyServer :8080/mywiki address, and refresh the page, things appear as expected.
if i make changes via the proxied virtual domain, then reload my page, the changes do not appear to have been written.
before moving to TiddlyServer, i ran this wiki successfully as a node.js server proxied, so i know that the proxy itself is not preventing put/get, etc.
The text was updated successfully, but these errors were encountered: